Skip to main content
Glama

Europe Instead

Search European tools

search_european_tools
Read-onlyIdempotent

European software tools by name or by category ("crm", "web analytics"), with optional filters on exposure level, country and open source. Needs a query or a category.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tools to return, at most 25. Default 10.
queryNoWords in the tool's name.
countryNoCountry of the contracting company, as an ISO 3166-1 code ("DE") or an English name ("Germany").
categoryNoA category by slug or name ("crm", "Web analytics"). See list_categories.
max_levelNoOnly tools whose exposure level, for who can reach the customer's data, is at most this (1: European stack; 2: European region, non-European provider; 3: Account or support data leaves Europe; 4: Core data leaves Europe on some paths; 5: Stored outside Europe by default). A level that is only a lower bound, because the subprocessor list is not complete, does not pass.
open_sourceNoOnly tools whose code is published under an open source licence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only the query-or-category requirement and the presence of filters, with no detail on result ordering, matching behavior, or what happens when filters exclude everything.

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?

Two short sentences with no padding, and the core resource is front-loaded. The fragmentary opening ("European software tools by name or by category") reads as a noun phrase rather than an action, which slightly hurts scannability.

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 would normally need to explain returns, but for a search tool the result shape is predictable, and the annotations carry the safety profile. The one non-obvious constraint, needing a query or category, is stated, leaving only ranking/pagination behavior unaddressed.

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 every parameter, including the nuanced max_level semantics, is documented in the schema itself. The description merely summarizes the filter set (exposure level, country, open source) without adding syntax or interpretation 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 states the resource (European software tools) and the two search axes (name/query or category), plus the optional filters. It is a sentence fragment missing an explicit verb, and it does not name a sibling it differs from, so it falls short of a 5.

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?

"Needs a query or a category" gives a real precondition that the schema does not enforce (required is 0), which is useful guidance. However, there is no when-to-use versus find_european_alternatives or list_categories guidance, and no statement of when this search is the wrong choice.

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