Skip to main content
Glama

Arquestra Consulting Market Radar

About the radar's data

about
Read-onlyIdempotent

What the Arquestra Consulting Market Radar covers and how it is built (sources, value band, window, classification), the date of the data, the licence (CC BY 4.0) and the attribution to give, the limits of this server and where to ask for more.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behaviour, so the safety bar is largely met. Beyond that, the description adds genuinely actionable context: the CC BY 4.0 licence, the attribution an agent must give, and that the server's limits are disclosed here — the attribution obligation is the kind of detail annotations cannot convey.

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?

It is a single sentence that front-loads the main subject ('what the radar covers and how it is built') and then enumerates the remaining payload items compactly. The parenthetical list is dense and slightly run-on, but every clause identifies an actual returned item, so little is wasted.

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 zero-parameter, annotation-covered, output-schema-less metadata tool, the description enumerates essentially the full payload an agent would need to know it exists and what it answers. A brief note on the response form (free text vs. structured) would make it complete, but nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter semantics are missing.

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 specifically what this tool returns: dataset coverage, build methodology (sources, value band, window, classification), data date, licence, attribution text, and server limits. That is clearly distinct from the data-retrieval siblings (get_firm, list_markets, search_tenders), though it never names them 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?

Usage is only implied: an agent can infer this is a metadata/documentation endpoint to consult for coverage, licensing, or attribution questions rather than for fetching records. There is no explicit 'use this when...' or 'do not use this to retrieve radar records' statement, leaving the routing to inference.

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