Skip to main content
Glama

Arquestra Consulting Market Radar

Get one market card

get_market
Read-onlyIdempotent

One market card (country x kind of work), as rebuilt every week: awards and values of the last 24 months, competition (bids, single-bid share), the top winners by awards and by value, SME share, price weight and award vs estimate, main buyers, trend, the open calls closing first and the contracts coming back in the next six months, each with its notice link, plus coverage, the page link and the citation; and the opportunity reading (firms active, median bids, single-bid share, each with its base, against the whole radar: a description of the market, never advice to bid). format=markdown returns the same card as Markdown.

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": {
      "country": "<country>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNoLeave this out. Set only by the radar's panel (MCP App) when the person uses its filters or 'show more' (panel), or by the site owner's own tests (dev), so that use is counted apart.
kindNoDefault all. procurement_advisory, statutory_audit, data_protection, hse_advisory: the subtype's card (advising public buyers on their tenders; audit of accounts; data protection officer; workplace health and safety advice), where it has one (ALL for Europe).
langNoLanguage of the page links (the data is the same). Default en.
pageNoPage of the open calls in the panel's list (25 a page). The card itself is the same on every page.
formatNoDefault json.
countryYesISO alpha-3 or alpha-2 code or a country name; ALL for Europe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Default all. procurement_advisory: the subtype's card (advising public buyers on their tenders), where it has one (ALL for Europe)."New value: +"Default all. procurement_advisory, statutory_audit, data_protection, hse_advisory: the subtype's card (advising public buyers on their tenders; audit of accounts; data protection officer; workplace health and safety advice), where it has one (ALL for Europe)."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "all",
      -  "strategy",
      -  "transformation",
      -  "platform",
      -  "build_run",
      -  "procurement_advisory"
      -]New value: +[
      +  "all",
      +  "strategy",
      +  "transformation",
      +  "platform",
      +  "build_run",
      +  "procurement_advisory",
      +  "statutory_audit",
      +  "data_protection",
      +  "hse_advisory"
      +]
  2. Changed4 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Default all."New value: +"Default all. procurement_advisory: the subtype's card (advising public buyers on their tenders), where it has one (ALL for Europe)."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "all",
      -  "strategy",
      -  "transformation",
      -  "platform",
      -  "build_run"
      -]New value: +[
      +  "all",
      +  "strategy",
      +  "transformation",
      +  "platform",
      +  "build_run",
      +  "procurement_advisory"
      +]
    • changedInput schema / properties / via / description
      Previous value: -"Leave this out. Set only by the radar's panel (MCP App) when the person uses its filters or 'show more', so that use is counted."New value: +"Leave this out. Set only by the radar's panel (MCP App) when the person uses its filters or 'show more' (panel), or by the site owner's own tests (dev), so that use is counted apart."
    • changedInput schema / properties / via / enum
      Previous value: -[
      -  "panel"
      -]New value: +[
      +  "panel",
      +  "dev"
      +]
  3. Changed2 schema fields changed
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Page of the open calls in the panel's list (25 a page). The card itself is the same on every page.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / via
      Added value: +{
      +  "description": "Leave this out. Set only by the radar's panel (MCP App) when the person uses its filters or 'show more', so that use is counted.",
      +  "enum": [
      +    "panel"
      +  ],
      +  "type": "string"
      +}
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world reads, so the safety profile is covered. The description still adds real value beyond them: the card is "rebuilt every week" (a freshness/staleness signal) and the opportunity reading is framed as "a description of the market, never advice to bid" (an interpretation guardrail). It does not cover failure modes for unknown country/kind combinations, which keeps it at a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the opening clause, but the rest is one ~110-word run-on sentence with a semicolon and a nested "plus" clause, making the field inventory hard to scan. Because there is no output schema, the return-content detail does earn some of its space, but it could be structured far more efficiently.

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 carries the full burden of explaining what comes back, and it does so thoroughly: metrics, coverage, page link, citation, and the opportunity reading with its base. The remaining gaps (behavior on unknown country, how "ALL" interacts with kind beyond the schema note) are minor for a read-only card fetch.

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 description coverage is 100% and every parameter (via, kind, lang, page, format, country) is documented in the schema, so the baseline is 3. The description's only parameter-relevant addition is "format=markdown returns the same card as Markdown," which largely restates the schema's format default rather than adding new meaning.

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?

"One market card (country x kind of work)" states a specific resource and scope, and the enumerated contents (awards, competition, winners, open calls) make clear this is a single-entity read, implicitly distinct from list_markets. It stops short of naming the sibling to use instead when the agent wants a list, so it is clear but not fully differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance: nothing says to prefer list_markets to browse markets or get_firm for a single company, and no prerequisites or error conditions are mentioned. The only usage-adjacent instruction ("Leave this out" for via) 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