Skip to main content
Glama

Europe Instead

Get a tool's facts and evidence

get_tool_details
Read-onlyIdempotent

One European tool in full: the facts behind its origin score and exposure level, each with its source URL, quoted passage and check date, plus its subprocessors and features.

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": {
      "slug": "<slug>"
    },
    "name": "get_tool_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe tool's slug, as returned by the other tools ("plausible").

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 already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the payload shape: facts with source URL, quoted passage and check date, plus subprocessors and features. It does not say what happens for an unknown or malformed slug, which is the main remaining gap.

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 sentence with no filler, and the key scoping ('One European tool') is front-loaded. The listing of returned components is dense but each item earns its place by telling the agent what evidence arrives.

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 must carry the return-value burden, and it does: the agent knows to expect sourced, dated facts plus subprocessors and features. It is not fully complete because failure behavior for an unresolvable slug is unstated, but for a single-parameter read tool this is close to sufficient.

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 slug parameter is documented in the schema with an example value, including length bounds. The description adds no further meaning about the slug, so the baseline of 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 and scope: a single European tool, returned with its origin-score and exposure-level evidence, subprocessors and features. That distinguishes it from the list/search siblings without needing to name them, though the retrieval verb is only implied by 'in full' rather than stated outright.

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 agent must infer that this is the drill-down call for one tool after a search or listing. There is no explicit when-to-use or when-not statement, and no mention of how to obtain the slug (that hint lives in the schema, not the description).

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