Skip to main content
Glama

get_site_plate

Read-only

Full plate for a slug, including verification, sources, and the canonical URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_site_plate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNo
slugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / site
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / slug / minLength
      Added value: +1
    • removedInput schema / required
      Removed value: -[
      -  "slug"
      -]
  2. Changed3 schema fields changed
    • removedInput schema / properties / site
      Removed value: -{
      -  "minLength": 1,
      -  "type": "string"
      -}
    • removedInput schema / properties / slug / minLength
      Removed value: -1
    • addedInput schema / required
      Added value: +[
      +  "slug"
      +]
  3. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful content context (verification, sources, canonical URL) that partly substitutes for the missing output schema, but says nothing about behavior on unknown slug/site, error cases, or whether all fields are always present.

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 compact sentence with the return contents front-loaded. No filler, though it is too short for what it needs to carry.

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?

With 0% schema coverage, no output schema, and a domain-specific term like "plate", the description should define the resource, both parameters, and expected failure modes. It leaves the meaning of "site", slug format, and the response shape entirely unaddressed.

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 coverage is 0% for both parameters with no descriptions or enums. The description mentions "slug" in passing but never defines the format, and the required "site" parameter is never referenced at all, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a getter for a "plate" keyed by slug, but "plate" is undefined jargon specific to this domain, so the agent can't tell whether it's a full record, a rendered document, or a status page. It is distinguishable from search_sites/list tools only by the word "Full", which is thin differentiation.

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

Usage Guidelines2/5

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

No statement of when to use this versus search_sites or get_species, and no prerequisites or exclusions. The only implicit cue is "Full", suggesting it's the detailed single-record fetch, but that must be inferred.

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