Skip to main content
Glama

verify_site

Idempotent

Check the server card published on a site and, if it matches, verify the Property and switch on its MCP endpoint. Returns the endpoint and, on the first successful verify only, the MCP API key agents use to call it. Safe to repeat.

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": {
      "propertyId": "<propertyId>"
    },
    "name": "verify_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyIdYesThe Property id from register_site

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, and the description corroborates the mutation while adding the crucial non-obvious detail that the MCP API key is returned only on the first successful verify. That one-time-secret behavior is exactly the kind of context annotations cannot convey. It still omits what happens when the server card does not match (error vs. silent no-op) and any auth requirements.

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 sentences, front-loaded with the action and side effect, followed by the return contract and the safety note. No filler, though the return-value and idempotency notes could be tightened 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 carries the return contract and does so: the endpoint plus the one-time API key. For a single-parameter mutating tool with annotations covering the risk profile, the only real gap is failure behavior when the published card does not match.

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, and the schema already explains that propertyId comes from register_site. The description adds no further constraints on the value (format, when it is stale, what an unknown id does), so 3 is the correct baseline.

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?

Specific verbs and resources: it checks the server card published on a site, verifies the Property, and enables its MCP endpoint. The read-then-mutate sequence is concrete enough that an agent knows what calling it accomplishes. It does not name a sibling it is distinguished from, which keeps it short of a 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 implied: the caller must already have a registered Property (the schema points back to register_site), and 'Safe to repeat' tells the agent retries are fine. There is no explicit statement of when to prefer this over check_site_readiness or site_status, or what prerequisites must hold before verification will succeed.

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