Skip to main content
Glama

Discover the Tools

validate_tool_submission

Read-onlyIdempotent

Validate the same fields as the website without saving. Returns a new idempotency key. Show all details and the private email to the user before calling submit_tool.

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": {
      "submission": "<submission>"
    },
    "name": "validate_tool_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
submissionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false. The description adds real value beyond them: nothing is persisted, a new idempotency key is returned, and private email data comes back and must be surfaced to the user. However, 'returns a new idempotency key' sits in mild tension with idempotentHint=true, and the description never says what a failed validation 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?

Three short sentences, front-loaded with the purpose before the return value and the workflow step. No filler, though the instruction to show details to the user is operational guidance that could be trimmed.

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

Completeness2/5

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

This is a complex tool: a nested payload with about twenty fields, zero schema descriptions, and no output schema. The description covers the happy-path return of an idempotency key but says nothing about the shape or content of validation errors, which is the whole point of a dry-run validator.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter is a nested object with roughly twenty undocumented properties carrying only length constraints and two enums. The description compensates only by deferring to 'the same fields as the website', which tells the agent nothing about which nested fields are required, their formats, or allowed values.

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?

States a specific verb and resource: validate the tool-submission fields without saving. The 'without saving' clause and the reference to submit_tool make the boundary with the sibling write tool clear, though 'the same fields as the website' points at an external artifact rather than naming the field set.

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 explicit sequencing: call this, show details and the private email to the user, then call submit_tool. That is a usable when-to-use rule. It does not state any when-not-to-use condition or what to do when validation fails.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources