Skip to main content
Glama

Maple Minute

Report a change to file

report_change

Tell us about a change we must file: new director, new address, shares sold and so on. The law allows 15 days.

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": {
      "id": "<id>",
      "change": "<change>"
    },
    "name": "report_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompany id like MM-12, from list_companies.
changeYesWhat changed and when, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context with the 15-day legal deadline, but it never says what actually happens on submission — whether a filing is submitted immediately, a task is queued, or a confirmation/fee is involved (notable given siblings like get_prices and get_payment_link).

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 followed by concrete examples plus the deadline. "And so on" leaves the scope open-ended, but nothing else is wasted.

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 two-parameter mutation with no output schema, the definition covers what to send and the deadline. It stops short of describing the outcome of the call or any caveats an agent should know before invoking it.

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 description coverage is 100%, so the schema already documents both parameters, including "What changed and when, in plain words" for the free-text field. The description's examples of reportable changes are mildly useful for populating that field but add no syntax, format, or constraint information beyond the schema.

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?

"Tell us about a change we must file" gives a clear verb and resource, and the examples (new director, new address, shares sold) concretely bound what counts as a reportable change. It does not differentiate itself from the sibling choose_new_name, even though a name change is plausibly one of the "and so on" cases covered here.

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 can infer this applies when a company has a statutory change that must be filed, and "the law allows 15 days" signals urgency. There is no explicit when-not guidance, no statement of prerequisites (an existing company id from list_companies is only mentioned in the schema), and no routing to alternatives such as choose_new_name.

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