Skip to main content
Glama

describe_contract

Read-only

Returns the citation contract for auditing biomedical evidence answers, including handle grammar, verdicts, flags, metrics, and instructions.

Instructions

The citation contract: handle grammar, verdicts, flags, metrics and instructions.

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_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
flagsYes
metricsYes
schemesYes
verdictsYesIn precedence order: first failure wins
instructionsYes
passage_pathsYes
handle_patternYes
contract_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description needn't restate safety. It adds that the payload is a contract covering grammar, verdicts, flags and metrics, but does not say whether the content is static, large, or intended as a primer before other calls — context that would help an agent decide to fetch it up front.

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 compact sentence with zero padding, front-loading the key noun 'citation contract'. It is terse to the point of being cryptic about jargon like 'flags' and 'metrics', 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 return values need no explanation, and with no inputs the surface is small. However, the description never explains the purpose of the contract within the workflow (interpreting citations/verdicts from sibling tools), leaving the agent to guess why and when to call it.

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 for the description to disambiguate; the baseline applies. No misleading hints about inputs are given.

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 names the resource ('The citation contract') and enumerates its contents — handle grammar, verdicts, flags, metrics, instructions — so an agent knows this is a reference/specification tool rather than a search or fetch tool. It lacks a verb, but the noun-phrase enumeration is specific enough to distinguish it from the search_/fetch_/resolve_ siblings.

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 when-to-use guidance at all: nothing says to call this before resolve_handles, or to interpret verdicts from audit_answer, or that it should be read once as setup. The agent must infer the trigger from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.