Skip to main content
Glama

Equitest

M&A period digest for an Insights report (admin)

ma_period_digest
Read-onlyIdempotent

Admin only. Computes every figure of an Equitest Insights M&A market report for one month, quarter or year from the Equitest M&A database: deal count, disclosed value, EV/EBITDA and EV/Revenue medians and quartiles with sample sizes, comparison with the previous period and the same period a year earlier, a 12-month / 8-quarter / 5-year trend, sectors (NAICS) with medians, target regions, buyer types, deal types, deal drivers, size buckets and the 10 largest disclosed deals, plus a data-coverage check and a writing guide. Call it first, write the report from it, then save with save_ma_insight. Amounts in USD millions.

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": {
      "period_type": "<period_type>",
      "period": "<period>"
    },
    "name": "ma_period_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodYesMonth "2026-09", quarter "2026-Q3" or year "2026"
period_typeYesReport period type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. Beyond that, the description adds the admin-only authorization requirement, the currency unit of every returned amount ("Amounts in USD millions"), and a data-coverage check, which are behavior facts the annotations do not carry.

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?

Front-loaded with the access restriction and purpose, followed by the workflow and units. The central inventory of metrics is a single dense run-on clause, but nearly every item earns its place because no output schema exists to describe the payload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 describing the return payload, and it does so item by item (medians, quartiles with sample sizes, prior-period and YoY comparisons, trends, sectors, buyer types, top 10 deals, coverage check). Access rules, units and the downstream save step are all present.

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% and both parameters are already documented with format examples ("2026-09", "2026-Q3", "2026") and an enum. The description only restates the month/quarter/year granularity, adding no syntax or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ("Computes") and a precisely scoped resource ("an Equitest Insights M&A market report for one month, quarter or year from the Equitest M&A database"), then enumerates the metrics produced. An agent can distinguish it from save_ma_insight (persistence) and search_ma_comparables (search) without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the call order: "Call it first, write the report from it, then save with save_ma_insight", naming the sibling to use afterwards. It also states an authorization precondition ("Admin only") that gates use, leaving nothing to infer about sequencing.

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