Skip to main content
Glama

Arquestra Consulting Market Radar

List the firms with a firm card

list_firms
Read-onlyIdempotent

Lists the consulting firms that win public contracts in Europe and have a firm card (the leading firms of each country), with awards in 24 months, value won, main country and kind of work, and the links to their card and page. Filter by country (firms with awards there), kind, or words of the name. Paged: up to 25 a page, 50 a query.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
langNoLanguage of the page links (the data is the same). Default en.
pageNo
queryNoWords of the firm's name.
countryNo
page_sizeNo

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 establish read-only, idempotent, non-destructive and closed-world behavior, so the description correctly focuses on other traits: it discloses the returned fields (awards in 24 months, value won, main country, kind of work, links) and, importantly, the paging ceiling (25 per page, 50 per query). The only shortfall is that the "50 a query" cap is worded ambiguously and result-ordering is not stated.

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 dense sentences, front-loaded with the resource definition before filtering and paging constraints. Slightly run-on, but every clause carries information an agent needs; no filler.

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 read-only, non-paginated-schema list tool with no output schema, the description covers what is returned, how filters behave, and the pagination limits, which is nearly everything required. The unexplained kind enumeration and unstated ordering keep it from being fully complete.

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?

With 33% schema coverage the description has to compensate and partly does: it explains that country matches firms with awards there (a non-obvious semantic), that query matches name words, and that page_size caps at 25. However, the kind enum values (strategy/transformation/platform/build_run) go unexplained, and lang and page are left entirely to the schema.

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 uses a specific verb and resource ("Lists the consulting firms that win public contracts in Europe") and bounds the scope further with "have a firm card (the leading firms of each country)" and a 24-month award window. This is clearly distinguishable from the singular get_firm sibling even though that sibling is not named 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?

The description explains how the three filters behave (country = firms with awards there, kind, name words), which implies the use cases, but it never states when to choose this over get_firm or search_tenders, nor any prerequisite. Guidance is inferable 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