Skip to main content
Glama

How the evidence works

get_methodology
Read-onlyIdempotent

Use this before interpreting confidence numbers or verification states, or when the user asks how facts are verified: source tiers, the confidence formula, the publishing gate per page type and the measured precision of the readers. Everything is read from the code that applies it.

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

Output Schema

NameRequiredDescriptionDefault
web_urlYes
source_tiersYes
confidence_capNo
index_thresholdYes
verification_statesYes
extraction_precisionNo
page_quality_weightsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond them: the values are read live from the code that applies them, signaling the agent that the returned methodology is authoritative rather than static prose. It doesn't discuss output shape or caching, but the output schema covers returns.

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?

One sentence, front-loaded with the usage condition and followed by a compact colon-delimited inventory of what it returns. Every clause earns its place and nothing is repeated from the title or schema.

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

Completeness5/5

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

For a zero-parameter, read-only documentation tool with an output schema, the description covers purpose, triggers, and content scope. An agent has everything needed to decide to call it and what to expect; return-value detail is rightly delegated to the output schema.

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 of 4 applies. The description correctly implies a single unfiltered fetch with no scoping arguments, which matches the empty schema.

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?

The description names the exact resource it returns — source tiers, the confidence formula, the publishing gate per page type, and reader precision — rather than restating the title. An agent can immediately tell this is the meta/documentation tool, distinct from the product-data siblings like get_product or get_statement.

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?

It gives two concrete invocation triggers: before interpreting confidence numbers or verification states, and when the user asks how facts are verified. It does not name a when-not condition or an alternative tool, but for a documentation lookup the trigger set is clear and actionable.

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