Skip to main content
Glama

get_methodology

Free. Exact formulas, sources and version of every metric.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden, and it does disclose cost ("Free") and response content (formulas, sources, version, coverage of "every metric"). It does not state that the operation is a safe read, how large the response is, or whether the version is a single global or per-metric value.

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 terse fragments that front-load the cost signal, which is the most decision-relevant fact for an agent deciding whether to spend a call. Nothing extraneous is present, though the terseness costs an explicit verb.

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 zero-parameter tool with no output schema, the description should say what the return payload is; it hints at fields (formula, source, version) but does not say whether these are per-metric records or one document. Adequate for a trivial call but leaves the response shape partly unknown.

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?

The tool takes zero parameters, so there is nothing to disambiguate beyond what the empty schema already shows; baseline 4 applies. The description correctly implies the call is unscoped ("every metric") rather than filtered.

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

Purpose3/5

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

The description names the resource implicitly (metric methodology: "exact formulas, sources and version of every metric") but supplies no verb, so the agent must infer that the tool returns documentation rather than metrics themselves. It is distinguishable from get_bank_metrics by returning formulas/sources rather than values, though that distinction is left for the agent to derive.

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 and no sibling is named as an alternative. The single word "Free" hints that this call carries no cost/credit, which is a weak contextual signal but not a usage rule.

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