Skip to main content
Glama

Europe Instead

Find European alternatives

find_european_alternatives
Read-onlyIdempotent

European software that replaces a non-European product ("Slack", "Google Analytics", "HubSpot"), in Europe Instead's ranking order. Each tool gives an origin score (how European the company is, 0 to 100) and an exposure level (1 to 5, who can reach the customer's data), both from sourced facts. Cite each tool's page.

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": {
      "product": "<product>"
    },
    "name": "find_european_alternatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many tools to return, at most 25. Default 10.
countryNoCountry of the contracting company, as an ISO 3166-1 code ("DE") or an English name ("Germany").
productYesThe non-European product to replace, by name or slug: "Slack", "Google Analytics", "hubspot".
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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely new behavior: results come in Europe Instead's ranking order and carry an origin score (0-100) and exposure level (1-5) derived from sourced facts, plus the instruction to cite each tool's `page`. It does not mention result counts or how ranking ties are broken.

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 tight sentences, front-loaded with what is returned before the scoring explanation. Every sentence carries information; only the quoted product examples are mildly redundant with the schema's own examples.

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 five parameters but no output schema, the description usefully documents the return shape (origin score, exposure level, citable page) and the ranking order. It leaves out pagination/result-count behavior beyond what `limit` implies, a minor gap for a read-only lookup tool.

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%, so the baseline is 3; the schema already defines limit, country, product, max_level with the full 1-5 exposure ladder, and open_source. The description reinforces the product examples and the exposure concept but adds little parameter detail the schema lacks, aside from clarifying that scores are fact-sourced.

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 concrete resource (European software replacing a named non-European product) and a concrete behavior (returns ranked results with origin score and exposure level). It never explicitly contrasts itself with the sibling search_european_tools, so differentiation has to be inferred from the 'replaces a product' framing.

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 implied by the phrase 'replaces a non-European product', which tells an agent this is the replacement-lookup path, but there is no explicit when-to-use/when-not guidance and no mention of search_european_tools or get_tool_details as follow-ups. An agent must infer the boundary from the tool name alone.

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