Skip to main content
Glama

search_legal_sources

Read-only

Retrieve passages from five frozen official EU legal/guidance source texts with versions and links. For an article follow-up use the returned official document URL plus Article number. Does not verify law as of today.

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": {
      "query": "<query>"
    },
    "name": "search_legal_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
required_groupsNo
limit_per_sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare this is a read-only, non-destructive, closed-world operation, so the bar is lower. The description nonetheless adds genuinely new behavioral facts: the corpus is a frozen snapshot, results carry versions and links, and the content is not a current-law verification — all of which affect how an agent should present 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?

Three short sentences, front-loaded with the core retrieval statement, and the currency caveat is placed last where it belongs. The follow-up sentence is slightly telegraphic but no filler is present.

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 zero schema descriptions, no output schema, and three parameters, the description leaves the two optional parameters entirely opaque. It adequately covers scope and currency limits but not enough for an agent to invoke the tool confidently with required_groups or limit_per_source.

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 description coverage is 0% and the description explains none of the three parameters. 'required_groups' and 'limit_per_source' (capped at 2) are undefined anywhere, so the agent must guess their meaning and effect; only 'Article number' loosely hints at query construction.

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?

Names a specific action (retrieve passages) and a specific resource (five frozen official EU legal/guidance source texts), with extra scope detail (frozen snapshot, versions and links). It is clearly distinguishable from a risk-case search, though it never names or contrasts the sibling explicitly.

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?

Gives one concrete follow-up rule ('For an article follow-up use the returned official document URL plus Article number') and one limitation ('Does not verify law as of today'), which implicitly warns against relying on it for current law. It does not say when to prefer or avoid it versus alternatives, so guidance is implied rather than explicit.

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