Skip to main content
Glama

Mastering Financial Markets

Request a company update

request_update
Idempotent

On explicit user request: one request from a registered user is enough, MFM processes it (no minimum number of requests; up to 5 requests per account per calendar month, UTC, on the site and through AI together, PDF and full combined; a repeat costs nothing). analysis=full queues full calculations for a level 3 company overnight, permanently, globally deduplicated by company. The default analysis=pdf queues PDF/interim reading within 7 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": {
      "company_id": "<company_id>",
      "user_requested_submission": "<user_requested_submission>"
    },
    "name": "request_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
analysisNofull: persistent level 3 full calculations overnight; pdf (default): PDF/interim reading within 7 days. Both count in the 5 requests per account per month
company_idYesMFM company id (from search or fetch) of the company for which the user explicitly asked an analysis on request.
user_requested_submissionYesMust be true, and only when the user explicitly asked to send this request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / analysis / description
      Previous value: -"full: persistent level 3 full calculations overnight, five new companies per UTC day per account; pdf (default): existing PDF service"New value: +"full: persistent level 3 full calculations overnight; pdf (default): PDF/interim reading within 7 days. Both count in the 5 requests per account per month"
    • addedInput schema / properties / company_id / description
      Added value: +"MFM company id (from search or fetch) of the company for which the user explicitly asked an analysis on request."
    • addedInput schema / properties / user_requested_submission / description
      Added value: +"Must be true, and only when the user explicitly asked to send this request."
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses the cost model (up to 5 requests per account per calendar month, UTC, across site and AI combined, PDF and full counted together), that repeats are free, the timing of each mode, and the global per-company deduplication. This is exactly the behavioral context an agent needs before spending a quota slot, and it is consistent with idempotentHint.

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?

The trigger condition is front-loaded and every sentence carries substantive information (quota, timing, dedup). However, the parenthetical quota sentence is very dense and semicolon-heavy, which slightly impedes scanning.

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 3-parameter queueing tool with a full schema and rich annotations, the description covers trigger, cost, timing, and deduplication, which is nearly everything needed to call it correctly. It does not suggest how to verify the request or check remaining quota afterward, a minor omission given no output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it clarifies that 'full' is persistent and level-3 overnight while 'pdf' is a 7-day interim read, and that both count toward the same monthly quota. The explicit-user-request framing reinforces the const=true on user_requested_submission without contradicting it.

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 concrete verb+resource pattern: it 'queues full calculations' or 'queues PDF/interim reading' for a company, and explains the trigger ('On explicit user request'). It does not explicitly contrast itself with siblings like quota_status or portfolio_calculator, so it falls short of full sibling differentiation, but the purpose is unambiguous.

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

Usage Guidelines4/5

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

The gating condition is explicit and front-loaded: use this only when the user explicitly asked, and one request from a registered user suffices. It also explains the choice between analysis=full and analysis=pdf (overnight persistent vs. 7-day reading). It stops short of naming which sibling to use for related tasks (e.g., checking quota before requesting).

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