Skip to main content
Glama

found-by-ai-monitor

Recent web mentions

get_mentions
Read-only

New pages on the web that mention the business, when a mention check has been run.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days (1-90, default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description need not restate safety. It does add genuine value by disclosing the prerequisite that a mention check must have been run, implying empty results otherwise. It says nothing about volume, ordering, or caching of results.

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?

One compact sentence with no filler, and the resource identification comes first. The trailing precondition clause makes it a sentence fragment, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with annotations covering the safety profile and no output schema, the description is nearly sufficient. It leaves the agent guessing about result volume, ordering, and what a 'mention' record contains, which are the remaining gaps an agent would want filled.

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% and the single optional 'days' parameter is fully documented in the schema (range 1-90, default 30), so the description carries no additional parameter burden. The description adds no syntax or default detail beyond the schema, which is the expected baseline here.

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 ('new pages on the web that mention the business') and a precondition ('when a mention check has been run'), so an agent knows it returns newly discovered mention pages rather than citations or traffic. It does not explicitly contrast itself with near-neighbours like get_citation_sources or get_source_profile, so it falls short of the sibling-differentiation bar.

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 statement of when to pick this tool over the many sibling getters, nor any exclusion. The only usage signal is the implicit 'mentions' framing plus the precondition that a mention check must have run, which is context rather than guidance.

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.