Skip to main content
Glama

M&A Target Screener

ma_screener
Read-onlyIdempotent

Banks scored as likely acquisition targets. (Source: BankRegReports (derived).)

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

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter state filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered elsewhere. The description adds only a provenance note ('Source: BankRegReports (derived)'), which is mild value, but says nothing about what the score means, how results are ordered or limited, or what happens when the state filter is omitted. For a screening/scoring tool, the methodology and default scope are exactly the missing behavioral context.

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?

Two short sentences, front-loaded with the core purpose and no filler. The brevity is appropriate structurally, though it shades into under-specification rather than crispness.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple: zero required parameters, one optional filter, flat schema, and annotations that cover the safety profile. Against that low complexity the description is close to adequate, but with no output schema present an agent still cannot tell what a result row contains (bank identity, score, rank?) or what the unfiltered default returns.

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 a single optional parameter with 100% schema description coverage ('Two-letter state filter'), so the schema already documents it fully. The description adds no syntax, default, or multi-state hints beyond that, which is the expected baseline when the schema carries the burden.

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

Purpose3/5

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

The description names a concrete output ('Banks scored as likely acquisition targets'), which tells an agent what the tool returns rather than merely restating the title. However, it is a noun phrase with no verb and no statement of scope (all banks vs. filtered), and it makes no attempt to distinguish itself from plausible siblings such as sec_ma_events or screener. Purpose is inferable but not sharply defined.

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 when-to-use guidance at all: no statement of what question this answers, no mention of when to prefer sec_ma_events or bank_peer_ranking, and no note on whether the state filter is required or optional. The agent must guess from the name alone.

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