Skip to main content
Glama

evidence_grades

Return the published E0–E4 evidence-grade definitions from the Signetex method page, not a true/false scale.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behavioral facts: the data is 'published' definitions sourced from the 'Signetex method page' (i.e., authoritative static content, not a computed result), and the return is a definition set rather than a boolean. What is missing is an explicit statement that the call is read-only and side-effect free, plus whether the returned definitions are stable/versioned.

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?

A single front-loaded sentence with zero filler: the action, the resource, the source, and the key disambiguation all land immediately. Nothing repeats the tool name or restates structured fields.

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?

For a zero-parameter, no-output-schema reference tool, the description supplies enough to call it correctly and to anticipate the kind of payload returned. A short note on whether the definitions are versioned or fixed, and confirmation that the call has no side effects, would close the remaining gap.

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 no parameter meaning to add beyond the schema; baseline for a 0-param tool is 4. The description correctly signals that no filtering or grade argument is accepted, which matches the empty object schema.

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?

States a specific verb ('Return') and a specific resource ('the published E0–E4 evidence-grade definitions from the Signetex method page'), so the agent knows this is a static reference lookup rather than a scoring calculation. The clause 'not a true/false scale' further pins down the shape of what comes back. It stops short of naming a sibling alternative, but the resource is distinctive enough to separate it from search_claims or latest_proof.

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?

Usage is only implied: an agent can infer it should call this when it needs the canonical meaning of E0–E4 rather than an entry's assigned grade. There is no explicit when-to-use or when-not-to-use statement, and no pointer to the sibling that returns actual graded evidence for a claim. Adequate but leaves routing to inference.

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