Skip to main content
Glama

Verify a submission

toolfound_verify_submission
Idempotent

Complete the mandatory ownership verification for a Toolfound submission using the verification token (from the email magic link, or after placing the meta tag / DNS TXT record on your domain, this call checks them on demand). Verification is what makes Toolfound listings trustworthy: every launched product is confirmed maker-owned. On success your launch is queued on the date you were assigned.

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": {
      "token": "<token>"
    },
    "name": "toolfound_verify_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesSecret verification token for one submission, found in the email link or in the meta tag or DNS record snippet shown after submitting. Treat it as a credential and use it only for your own submission.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / token / description
      Previous value: -"The verification token from your submission email or verification snippet."New value: +"Secret verification token for one submission, found in the email link or in the meta tag or DNS record snippet shown after submitting. Treat it as a credential and use it only for your own submission."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the call actively fetches the meta tag or DNS TXT record on demand, and that success causes the launch to be queued on the assigned date — real behavioral consequences not captured by the hint fields. It is consistent with idempotentHint=true and destructiveHint=false, though it does not mention failure modes or how long verification takes.

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?

The action and its mandatory nature are front-loaded, and each sentence adds something: how to verify, why it matters, and what happens on success. The parenthetical in sentence one is dense and slightly awkward, which keeps it from a 5.

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 one-parameter mutation tool with no output schema, the definition covers what to supply, where it comes from, what the call does mechanically, and the resulting state change. An agent has everything needed to invoke it correctly, with only error-case detail 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?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaningful provenance for the single parameter: the token comes from the email magic link or from the meta tag / DNS snippet, and is treated as a credential. That complements the schema's secrecy note with where to actually find the value.

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 a specific verb and resource: 'Complete the mandatory ownership verification for a Toolfound submission.' It also implies a distinction from a passive check by noting 'this call checks them on demand,' but it never names the sibling toolfound_check_verification, so the differentiation is left to inference.

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 implied rather than stated: the verification is 'mandatory' and requires a token, so an agent can infer it must be called after submitting. There is no explicit when-not-to-use guidance and no direct routing to toolfound_check_verification for status-only queries.

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