Skip to main content
Glama
Sign In
numproof

numproof

by projecttron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

verify_claim

Verify any math or finance claim and obtain a definitive VERIFY, REFUTE, or ABSTAIN result with an accompanying certificate or counterexample.

Instructions

Exactly verify a math/finance claim -> VERIFY/REFUTE/ABSTAIN with certificate and counterexample.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "claim": "<claim>"
    },
    "name": "verify_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

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. It discloses the three possible outcomes and mentions that a certificate and counterexample accompany the result. However, it doesn't state whether any side effects exist or clarify the nature of the certificate, leaving some ambiguity.

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?

The description is a single, focused sentence that front-loads the purpose and outcome. No filler words; every element earns its place.

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 simple one-parameter tool, the description covers the core function and return categories, but lacks details on input formatting, the certificate's structure, and when ABSTAIN occurs. The absence of an output schema makes these omissions more significant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has one parameter 'claim' with 0% coverage, so the description must compensate. The phrase 'math/finance claim' adds domain context to the parameter, but it doesn't specify the expected format or provide examples, leaving the agent to infer.

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 uses a specific verb 'verify' and names the resource as 'math/finance claim'. The arrow and outcome labels (VERIFY/REFUTE/ABSTAIN) clearly distinguish it from siblings like audit_rows or diff_rows, which address different operations.

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?

The description implies usage for verifying math/finance claims but offers no explicit guidance on when to choose this tool over siblings, no alternatives mentioned, and no exclusions. Context is present but shallow.

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

Deploy Server

Other Tools