Skip to main content
Glama
Foto MCP Server
by thesven

foto_check_username

Check if an @username is available on Foto by validating its length and alphanumeric format, then querying the usernames registry so you can choose a usable handle.

Instructions

Check whether an @username handle is available on Foto (verifying length, alphanumeric characters, and querying the usernames registry).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "foto_check_username"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesThe username handle to check (with or without leading '@')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real value by naming the internal checks performed (length, alphanumeric characters, registry lookup), which tells the agent this is a read-only validation rather than a reservation. It still omits auth requirements, whether the handle is held/reserved, rate limits, and above all what a positive vs. negative result looks like.

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?

A single front-loaded sentence with zero filler; the parenthetical efficiently packages the validation steps. Slightly dense but every clause earns its place.

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

Completeness3/5

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

For a one-parameter validation check there is no output schema, so the description should signal what comes back — an availability boolean, and ideally the failure reason when a handle is invalid or taken. The agent knows how to call it but not how to interpret the response, leaving a meaningful gap.

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

Parameters3/5

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

Only one parameter exists and schema description coverage is 100%, with the schema itself documenting the optional leading '@'. The description's '@username handle' framing is consistent with the schema but adds no syntax or format meaning beyond it, so the baseline 3 applies.

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

Purpose4/5

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

Names a specific verb ('Check') and a specific resource ('whether an @username handle is available on Foto'), which no sibling tool covers — the nearest siblings, foto_get_user_profile and foto_list_profiles, look up existing users rather than test availability. It stops short of naming an alternative or contrasting, so it earns 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the description makes clear it is a pre-flight availability check, so an agent can infer it belongs before account creation or handle selection. There is no explicit statement of when to prefer it, no prerequisites (auth requirements), and no exclusions.

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