Skip to main content
Glama

Describe Sahadeva methodology

describe_methodology
Read-onlyIdempotent

Returns the calculation boundary, accuracy status, interpretive safety contract and production validation requirements.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
computationYes
interpretationYes
productionGateYes
currentAccuracyYes
supportedMethodologyYes
calculationComponentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / calculationComponents
      Added value: +{
      +  "type": "array"
      +}
  2. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds that the payload is a fixed policy/contract artifact rather than chart-specific data, which is genuinely useful context. It stops short of saying whether this is static text that never varies by chart or input.

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?

A single front-loaded sentence with no filler; every listed item conveys content. It is slightly dense as a comma-separated inventory, but nothing 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?

An output schema exists, so detailing return values is not strictly required, and the description is adequate for a zero-param read. The gap is routing: with ~90 siblings, an agent lacks the cue for when this methodology endpoint is the right call versus knowledge_status or suggest_safe_practice.

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 the baseline is 4. Nothing in the description misleads about inputs, and no parameter explanation is needed.

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 gives a specific verb ('Returns') and enumerates the exact contents: calculation boundary, accuracy status, interpretive safety contract, production validation requirements. That is far more informative than the name alone. It does not, however, distinguish this static methodology read from adjacent status/convention tools such as knowledge_status, get_synthesis_validation_status, or compare_conventions.

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 statement of when an agent should call this versus the many sibling audit/status/knowledge tools, and no prerequisites or exclusions. The agent must infer that this is a documentation lookup rather than a per-chart analysis.

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