Skip to main content
Glama

Share Issuance Dilution

bpj_equity_issuance_dilution
Read-onlyIdempotent

Compare an existing holder’s ownership before and after an issue assuming no participation in the new shares.

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": {
      "prior": "<prior>",
      "held": "<held>",
      "newShares": "<newShares>"
    },
    "name": "bpj_equity_issuance_dilution"
  }
}

Input Schema

NameRequiredDescriptionDefault
heldYes
priorYes
newSharesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/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 one genuinely useful behavioral detail — the no-participation modeling assumption — but does not disclose what is returned (ownership percentages, dilution delta, or absolute share counts) despite there being no output schema.

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?

A single well-formed sentence with the key assumption front-loaded and no wasted words. It is efficient, though the terseness comes at the cost of the parameter and return-value detail noted elsewhere.

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?

For a simple three-integer calculator with annotations covering safety, the description is adequate to understand intent. However, with no output schema, an agent cannot tell whether the result is a percentage, a ratio, or a share count, and the parameter roles remain ambiguous — both gaps the description should have closed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden of explaining the three inputs, and it largely does not. It never clarifies that 'prior' is fully diluted shares outstanding versus 'held' being the holder's slice, nor that held should not exceed prior, nor any unit or rounding behavior.

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 a specific operation: comparing an existing holder's ownership before and after a share issue. It clearly names the resource (ownership/dilution) and the temporal framing (before vs. after). It does not differentiate from any sibling, but the siblings listed are unrelated calculators, so the purpose stands on its own.

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 explicit when-to-use or when-not-to-use guidance, no mention of alternatives, and no stated prerequisites. The only contextual signal is the embedded assumption of 'no participation in the new shares,' which implies a scenario but does not guide tool selection.

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.