Skip to main content
Glama

LivedProof (demo)

Explain proof levels

proof_levels
Read-only

What LivedProof's proof levels (1-3) mean and what each requires.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered by structured data. The description adds that the content is a definitional mapping of levels 1-3, but says nothing about the form of the response (prose, table, per-level entries) or whether it is static versus account-specific.

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?

One short sentence with no filler, and the key scoping detail (levels 1-3) is front-loaded. The phrasing is a noun clause rather than a verb phrase, which is slightly less directive than it could be.

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 explainer with no output schema, the description covers the topic but leaves the return shape and the relationship to sibling tools unstated. It is adequate to call correctly but not fully self-sufficient for an agent deciding whether this or another lookup tool answers its question.

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?

Zero parameters, so the baseline is 4. The description does add useful semantics by bounding the domain to levels 1-3, telling the agent what range of values it will learn about, but there are no parameters whose meaning needs explaining.

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?

Names the exact resource (LivedProof's proof levels) and the exact scope (levels 1-3, what each means and requires), so an agent knows this is a static reference/explainer rather than a lookup of live data. It does not explicitly contrast itself with siblings like lookup_tool or get_verified_answers, keeping it short of a 5.

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 should call it when it needs to interpret a proof level. There is no explicit 'use this before/after X' or exclusion against lookup_tool or get_verified_answers, though the sibling names suggest distinct roles.

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