Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
verify_calculationB

Check a claimed numerical result. Request fields: calculation_type, claimed_result, inputs, optional tolerance. Returns passed/failed and independently calculated result. Claim-vs-source categories (quote_in_text, number_in_text, date_in_text) take source_text you supply plus claim_text (or claimed_result for numbers); they prove only that the supplied text contains the claim, not that it is true.

verify_batchA

Check up to 50 numerical claims in one call. Each item has calculation_type, claimed_result, inputs and optional tolerance.

verify_and_signB

Check a numerical claim and issue a locally signed Ed25519 receipt. The signature proves integrity and local issuer identity, not the truth of supplied inputs.

check_signed_receiptB

Check whether an AgentVerify receipt has an intact signature from this local issuer.

get_public_keyB

Return the public signing key for this AgentVerify instance.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct operation: single verification, batch verification, verification with signing, receipt signature check, and public key retrieval. The only mild overlap is between verify_calculation and verify_and_sign, but the descriptions make the signing distinction explicit.

Naming Consistency5/5

All names are snake_case and verb-led (verify_*, check_*, get_*), forming a predictable pattern throughout. verify_and_sign is slightly longer but still follows the convention.

Tool Count5/5

Five tools is well-scoped for a verification-and-signing service, with each tool earning its place. No redundant or filler tools are present.

Completeness4/5

The surface covers the core lifecycle: verify, batch verify, sign, check receipt, and retrieve public key. Minor gaps exist, such as no batch signing or receipt listing/retrieval, but core workflows are covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues