Skip to main content
Glama

Vermeldingen / Mentions

mentions
Read-onlyIdempotent

External mentions of 'tachtien' (tweets, press and Cityguys articles) with title, source and URL. The url is null for a mention without a link.

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

Input Schema

NameRequiredDescriptionDefault
sourceNoOnly mentions from this source

Output Schema

NameRequiredDescriptionDefault
mentionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one useful behavioral nuance — that url is null when a mention has no link — but says nothing about result ordering, volume, or pagination, so it adds some value without being rich.

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?

Two short sentences, scope stated first, the null-URL caveat second. Nothing is redundant and nothing needs to be re-read.

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?

For a zero-required-parameter listing tool with a documented enum and an existing output schema, the description covers purpose, scope, and the main edge case (null URL). Only minor operational details — ordering and result size — are absent, and the output schema plus annotations absorb most of that burden.

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?

The single optional 'source' parameter has 100% schema description coverage and an enum of twitter/press/cityguys, so the schema carries the semantic load. The description adds nothing beyond it (no note that omitting source returns all sources), 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 the resource precisely ('external mentions of tachtien') and enumerates the sub-kinds (tweets, press, Cityguys articles) plus returned fields (title, source, URL), so an agent knows exactly what it retrieves. It does not explicitly contrast with siblings, but define/examples/is_tachtien/tachtienify are unrelated enough that differentiation is not a real risk.

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 only implied: the description makes clear this lists mentions, but it gives no when-to-use condition, no exclusion, and no mention of ordering, limits, or whether the list is exhaustive. For a simple read tool with an optional filter, that is the minimum viable level rather than a genuine gap.

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.