Skip to main content
Glama

Finance education article — Atom

Finance education article

finance_education_article
Read-onlyIdempotent

Submits a finance-education article-production record (article structure, worked example, no-signals discipline, disclosures, review) and returns a deterministic ARTICLE_READY / NOT_ARTICLE_READY / INSUFFICIENT_EVIDENCE verdict across five sections, including computed section-order and worked-example arithmetic checks, with per-check evidence. Audits the declared record; it writes no article.

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

Input Schema

NameRequiredDescriptionDefault
topicNoArticle topic.
reviewNoReview evidence.
articleNoArticle being audited.
signalsNoSignals evidence.
structureNoStructure evidence.
disclosureNoDisclosure evidence.
worked_exampleNoWorked example evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description meaningfully adds that verdicts are deterministic, that five sections are checked including computed section-order and worked-example arithmetic, that per-check evidence is returned, and that no article is written—behavior an agent could not infer from the annotations alone.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and the return contract, then closed with the scope-limiting clause. Dense but no filler; every clause carries information the agent needs.

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?

Given seven optional nested parameters, no output schema, and a niche audit workflow, the description covers purpose, verdict taxonomy, check types and side-effect posture adequately. Minor gap: it does not say what a minimally valid record looks like despite zero required parameters, which an agent might need to avoid trivial INSUFFICIENT_EVIDENCE calls.

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 per-parameter baseline is 3. The description adds value by naming the record's component concerns (article structure, worked example, no-signals discipline, disclosures, review), which maps onto the structure/worked_example/signals/disclosure/review parameters and clarifies that "signals" means a no-signals discipline rather than a data feed.

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

Purpose5/5

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

Uses a specific verb ("Submits... record"/"Audits") tied to a precise resource (finance-education article-production record) and enumerates the outcome space (ARTICLE_READY / NOT_ARTICLE_READY / INSUFFICIENT_EVIDENCE). The closing clause "Audits the declared record; it writes no article" sharply bounds what the tool is and is not, so an agent cannot mistake it for an article generator.

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?

The description implies the use case (validating a declared article-production manifest across five sections) but never states when to call it versus not call it, nor any prerequisites such as requiring a fully populated record. With no sibling tools to route against, implied usage is the practical ceiling, but explicit context would still help.

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.