Skip to main content
Glama

Equitest

List Equitest Insights M&A reports (admin)

list_ma_insights
Read-onlyIdempotent

Admin only. Lists the Equitest Insights M&A market reports (drafts and published) with period, status, last update and the public or preview URL.

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_ma_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond the annotations: an admin-only authorization requirement and the fact that both draft and published records are returned, though it says nothing about pagination or ordering.

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 with no filler, and the most operationally important constraint ("Admin only") is front-loaded before the description of what is returned.

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 simple, single-parameter read tool with no output schema, the description does the heavy lifting by naming the returned fields and the admin restriction. The only meaningful gap is the unexplained status filter behavior, which is minor given the self-describing enum.

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?

There is one parameter with 0% schema description coverage, so the description must compensate. It mentions drafts and published, which loosely maps to the status enum, but never explains the 'all' default or that the enum filters results, leaving the parameter's semantics to the enum values alone.

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 Equitest Insights M&A market reports") and enumerates the returned fields (period, status, last update, public/preview URL), so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from siblings like ma_period_digest or save_ma_insight, which keeps it short of a 5.

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?

"Admin only" provides a clear access precondition and "drafts and published" implies the tool spans both states, but there is no explicit when-to-use guidance, no exclusions, and no pointer to the sibling that creates reports (save_ma_insight). Usage is therefore implied rather than stated.

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