Skip to main content
Glama

Discover the Tools

submit_tool

Idempotent

WRITE: Save one free tool suggestion privately for editorial review. Requires explicit user confirmation of all submitted details, the private contact email and review conditions. No publication or email is triggered. Reuse the validation idempotency key unchanged for retries; keep the returned tracking secret private.

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>",
      "idempotency_key": "<idempotency_key>",
      "confirmed": "<confirmed>"
    },
    "name": "submit_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmedYesTrue only after the user explicitly approves sharing these details and private contact email for editorial review.
submissionYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, and the description adds genuinely new behavioral facts: nothing is published and no email is triggered, the returned tracking secret must be kept private, and retries must reuse the idempotency key unchanged. The one gap is that the effect of the review workflow after submission (timeline, what happens on rejection) is not described, but that is beyond the call itself.

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?

Four compact sentences, front-loaded with the WRITE marker and the core action, then preconditions, then side-effect disclaimers, then retry handling. Every sentence adds information; the only minor cost is that the precondition clause is dense and packs three distinct requirements into one sentence.

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

Completeness4/5

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

With no output schema, the description compensates by telling the agent that a tracking secret is returned and must be kept private, and it clarifies the privacy and no-publication guarantees of a submission that involves a private email. For a three-parameter, deeply nested mutation whose schema documents only a third of its fields, a little more guidance on the submission payload would be the remaining 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?

Schema description coverage is only 33% and the submission object is nested with roughly twenty sub-fields, so the description carries some burden. It does add meaning for two of the three top-level parameters: 'confirmed' is tied to explicit user approval of the private contact email and review conditions, and the idempotency_key is framed as the validation key that must be reused on retries. The many nested submission fields (pricing, platforms, relationship, use cases) get no explanation at all.

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?

The description opens with an explicit 'WRITE:' marker and a specific verb+resource ('Save one free tool suggestion privately for editorial review'), which lets an agent distinguish this mutation from read-oriented siblings like get_tool or search_tools. It also implicitly positions itself downstream of validation by referring to the validation idempotency key, though it never names a sibling outright.

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?

It states clear preconditions for invocation: explicit user confirmation of all submitted details, the private contact email, and the review conditions, plus the retry rule (reuse the same idempotency key). It does not explicitly say when not to call it or point to validate_tool_submission as the prerequisite step, so the guidance is strong but not complete.

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