Skip to main content
Glama

AI answer checks

answer_checks
Read-onlyIdempotent

Answer checks for one website: whether search-backed assistants (ChatGPT, Perplexity) name or cite the site for its buyer questions, this week and the 8 before. An input, not a score. locked=true means the plan does not run checks.

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": "answer_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the 9-week time window, the 'An input, not a score' framing of the output, and the meaning of locked=true when the plan does not run checks. It does not describe pagination or result shape, but an output schema exists to carry that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with what the tool returns and scoped with the time window before the two clarifying caveats. No filler, and every sentence carries information the agent needs.

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 an output schema present, the description need not explain return values, and it covers scope, time range, output semantics and the locked-plan case. The only real gap is routing guidance relative to its many siblings, which the description never addresses.

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 coverage is 100% with a single optional website_id, and the schema already explains the uuid/domain forms and the omit-when-single-website case. The description reinforces the one-website scope but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 names a specific resource (answer checks for one website) and states exactly what is measured: whether ChatGPT/Perplexity name or cite the site for its buyer questions. That is far more specific than the title. It stops short of naming the sibling tools it differs from (e.g. ai_crawlers, insights), so an agent must infer the boundary from context.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. 'For one website' and the 9-week window imply a read-only visibility check, leaving the agent to infer when this is preferable to analytics_snapshot or ai_crawlers.

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