Skip to main content
Glama
Sign In

FileFleet

by io.filefleet
OverviewDiscussionsAdmin

Find upload requirements

find_upload_requirements
Read-onlyIdempotent

Look up what size, format or dimensions a photo or upload must be for a specific form: US passport photo size, US visa or DS-160 photo requirements, Green Card (DV) lottery photo rules, Schengen visa photo size, UK online passport photo rules, or IBPS photo, signature, thumb impression and declaration sizes. Returns pixel sizes, file size limits, head and eye position rules, the official source and the date checked, plus a free FileFleet page that makes a photo that passes on the person's own device. Leave the query empty to list everything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_upload_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWhat the person is applying for, such as "US visa photo" or "IBPS signature".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is free. The description adds genuinely new behavioral content: what the response contains (pixel sizes, file size limits, head/eye position rules, official source, date checked) and that the referenced FileFleet page is free and runs on the person's own device. It does not discuss rate limits or freshness guarantee details beyond 'date checked'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, and the long enumeration of covered forms and returned fields is dense but informative rather than padded. The promotional mention of a free FileFleet page is on the edge of marketing copy, though it does carry usable context; overall it is a little long for a one-parameter read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional-parameter, read-only lookup with no output schema, the description covers scope, return contents and the empty-input case. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Coverage is 100% and the schema already gives an example, so baseline would be 3. The description earns above baseline by documenting the otherwise non-obvious empty-query behavior (list everything), which is a semantic the schema does not express.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ('Look up what size, format or dimensions a photo or upload must be for a specific form') and then enumerates the exact document classes covered (US passport, DS-160, DV lottery, Schengen, UK online passport, IBPS). An agent can tell this is a photo/upload specification lookup rather than a file inspector or link builder.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete operational rule for the empty-query case ('Leave the query empty to list everything') and makes the covered scope explicit through the enumerated form types. It does not state exclusions or name when to prefer a sibling such as make_requirement_link, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FileFleet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources