Skip to main content
Glama

Check verification status (dry run)

toolfound_check_verification
Read-onlyIdempotent

Non-destructive dry run of ownership verification for a Toolfound submission: reports, per method, what the checker sees RIGHT NOW, meta tag found or not (with the exact expected tag), DNS TXT found or not (with the exact expected record), and whether the submission email qualifies for the magic-link path. Use it to distinguish 'my deploy is not live yet' from 'wrong token' before calling toolfound_verify_submission. Changes nothing.

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_check_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe verify_token returned by toolfound_submit_product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower; the description adds genuinely new behavioral context by describing what is inspected per verification method and emphasizing the snapshot nature ('what the checker sees RIGHT NOW'). 'Changes nothing' restates destructiveHint=false, which is mild redundancy rather than added value.

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 dense sentence that is front-loaded with the operation and then the use case; every clause (expected tag, expected DNS record, magic-link eligibility) delivers information. It reads slightly run-on and carries one redundant clause ('Changes nothing') already implied by annotations.

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 usefully pre-describes the return shape per method and notes that exact expected values are surfaced. It omits error behavior for an invalid or unrecognized token, which is a minor gap for a one-parameter check tool.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that it is the verify_token from toolfound_submit_product. The description adds only indirectly, via the framing of 'ownership verification for a Toolfound submission'; the baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific verb and resource — a non-destructive dry run of ownership verification for a Toolfound submission — and enumerates exactly what is reported per method (meta tag found/not, DNS TXT found/not, magic-link email qualification). It is clearly distinguishable from toolfound_verify_submission, which it explicitly defers to.

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

Usage Guidelines5/5

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

It states both when to use it and why: 'before calling toolfound_verify_submission', to distinguish 'my deploy is not live yet' from 'wrong token'. This is an explicit alternative with an explicit selecting condition, so an agent has no inference left to do.

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