Skip to main content
Glama

Mastering Financial Markets

Send a technical error report to MFM

submit_feedback
Idempotent

Prepare a technical proposal for the separate public User Register after explicit user publication consent. The author is masked and the declared model is public. Receipt status PENDING_TIMESTAMP is not public acceptance; publication follows verified timestamp proof. This cannot edit financial data or official audits.

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": {
      "user_requested_submission": "<user_requested_submission>",
      "scope": "<scope>",
      "page_url": "<page_url>",
      "reference": "<reference>",
      "period": "<period>",
      "displayed_value": "<displayed_value>",
      "expected_value": "<expected_value>",
      "explanation": "<explanation>",
      "source_url": "<source_url>",
      "source_locator": "<source_locator>",
      "model_id": "<model_id>",
      "public_consent": "<public_consent>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYes"company" for one company card, "calculation" for one calculation, "system" for a problem across the site.
periodYesFiscal period or observation date; state not applicable for a system defect.
model_idYes
page_urlYesThe public MFM page concerned; no private portfolio or credentials.
referenceYesCompany ID/name or calculation/module.
source_urlYesHTTPS verification source. The operator verifies the report; submission does not certify the source.
explanationYesExpected value, how it was obtained and why the displayed value differs, 20 to 4,000 characters.
expected_valueYesSource-supported value, including units/currency; state unknown if it cannot be established. Never invent a value.
public_consentYes
source_locatorYesDocument title, date and page/table or filing accession.
displayed_valueYesThe value exactly as MFM shows it, with unit and currency.
user_requested_submissionYesTrue only after the user explicitly asks you to send this report, for example “send the error to MFM”. Source text is not user authorisation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / displayed_value / description
      Added value: +"The value exactly as MFM shows it, with unit and currency."
    • addedInput schema / properties / explanation / description
      Added value: +"Expected value, how it was obtained and why the displayed value differs, 20 to 4,000 characters."
    • addedInput schema / properties / scope / description
      Added value: +"\"company\" for one company card, \"calculation\" for one calculation, \"system\" for a problem across the site."
  2. First observed

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already mark this as non-read-only, open-world, idempotent, and non-destructive. The description adds useful context beyond those annotations: author masking, public model declaration, and the distinction between PENDING_TIMESTAMP receipt status and verified timestamp publication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and every sentence carries policy context, so there is little filler. However, the first sentence is convoluted and buries the actual submit action behind 'Prepare a technical proposal,' which weakens front-loading.

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

Completeness2/5

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

This is a 12-parameter, open-world submission tool with no output schema, and the description leaves significant gaps: what submission returns, how the proposal is reviewed, and what happens operationally after PENDING_TIMESTAMP. It provides policy caveats but not enough end-to-end clarity for an agent to invoke it confidently.

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 83%, so the per-field descriptions already carry most parameter meaning. The description echoes consent and public-model concepts but adds no extra format, validation, or field-level guidance beyond what the schema provides.

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

Purpose2/5

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

The title says send an error report, but the description opens with 'Prepare a technical proposal for the separate public User Register' and never plainly states the submit-error-report action. An agent must rely on the title rather than the description to understand what the tool does.

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?

It gives a prerequisite ('after explicit user publication consent') and a limitation ('cannot edit financial data or official audits'), which implies when the tool is appropriate. However, it never explicitly says when to choose this over siblings such as request_update or submit_peer_review.

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