Home / Businesses / File Naming Convention Check
File Naming Convention Check
Check file names against your naming convention (date, client code, title, version) and get the fixed name for each, with Windows character and reserved-name problems flagged and a signed record.
Testing
- What it does
- Check file names against your naming convention (date, client code, title, version) and get the fixed name for each, with Windows character and reserved-name problems flagged and a signed record.
- Who it is for
- Businesses.
- Start in one step
- Ask your agent to call
file_name_checkat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
File Naming Convention Check is for agents that file documents in a shared drive for a business and must keep names in the house convention so files sort, search and hand over cleanly. Check file names against your naming convention and get the fixed name. Send up to 50 file names and the pattern: which parts in which order (date, client, title, version), the separator, the date format (YYYY-MM-DD or YYYYMMDD), the version form (v01), the title form (lower-case words joined by '-'), your client codes and allowed extensions. Get back, per name: ok, fix (with the suggested name and every change made) or cannot_fix (with the reason: an ambiguous date such as 04-05-2026, no client code found, an extension not allowed, a suggested name that would collide with another file). Also flags characters Windows does not allow, reserved names such as CON, names ending in a space or dot, spaces, non-ASCII letters and over-long names. File names only: do not send names of people, emails or ID numbers (they are refused when they look like them). It is one of the Files and records department tools LLPRO builds for the work agents do across business software (Google Drive, Dropbox, OneDrive, Box). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents that file documents in a shared drive for a business and must keep names in the house convention so files sort, search and hand over cleanly.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call, names up to 50 entries, parts up to 4 entries, client_codes up to 200 entries, extensions up to 50 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not open, read or rename files: it works on the names you send and suggests names only. Does not see folders, so it cannot tell whether a suggested name already exists outside the list. Cannot tell a person's name from an ordinary word: do not send file names that hold people's names (emails, web addresses, Social Security and phone shapes, and any run of more than 8 digits once dates are cut out, are refused; so a camera name with a 9-digit time such as PXL_20260314_120000123 is refused, IMG_20260314_120000 is not). Does not read two-digit years or month names (14 March 2026) as dates. Keeps only the last extension: archive.tar.gz keeps gz and 'tar' becomes a title word. Does not know your records policy or which version is current. Other systems have extra limits (SharePoint and OneDrive block some names and characters; full paths may be limited to 260 characters on older Windows): check those where your files live.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "file_name_check", "arguments": {"names": ["2026-03-14_ACME_board-minutes_v02.pdf", "ACME Board Minutes 3-14-2026 v3.PDF"], "client_codes": ["ACME"]}}}For agents
Tool file_name_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:jkwfsx3i3jlh4fmhetuuj2ljcm): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): vx/N8fcukqPVqkmnneWNYwHbnxwisIQK/FsvXANz3Bc=
For agents that search MCP registries for file naming convention, file name check, rename files tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: Checking names is one step of filing documents. Tell the Hub the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card