Skip to main content
Glama

The Right Accountant Research Data

Get UK accountancy research

get_accountancy_research
Read-onlyIdempotent

Return one of the research datasets: "research" (ownership, size, age), "filing-health" (overdue filings) or "accounts-calendar" (filings due by month). Aggregate figures only, from Companies House data.

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": {
      "dataset": "<dataset>"
    },
    "name": "get_accountancy_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 safety is covered. The description adds genuinely new behavioral context: results are aggregate figures only (no record-level rows) and are sourced from Companies House data, which sets expectations about granularity and provenance.

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

Conciseness5/5

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

Two short sentences, front-loaded with the return action, then the three dataset meanings, then the aggregate/provenance caveat. No filler or restated title.

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 single-parameter, read-only, closed-world tool with full annotation coverage and no output schema, the description supplies what matters: the three dataset choices and the aggregate-only nature of the data. Only minor gaps remain around output shape and whether the datasets require any parameters beyond selection.

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?

Schema coverage is 0%, so the description must carry the parameter meaning, and it does: each of the three enum values is defined ('research' = ownership/size/age, 'filing-health' = overdue filings, 'accounts-calendar' = filings due by month). It stops short of saying what each dataset's output looks like or how large it is.

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 ('Return') plus a concrete resource ('research datasets') and names all three dataset variants with a parenthetical hint of their contents. An agent knows exactly what comes back at a category level, though the broad labels ('age', 'size') are not pinned to units or fields.

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: the agent must pick one enum value, and the parentheticals hint at which to choose for ownership/size/age questions versus overdue-filing questions versus due-date questions. There is no explicit 'choose X when you need Y' routing language, and no siblings exist to compare against.

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