Skip to main content
Glama

SCRIPTMASTERLABS — Agent Verify

Proof Score methodology

methodology
Read-onlyIdempotent

Return the published Proof Score methodology and its version: the inputs (Proof Records only), the recency half-life decay, the 1/k wash decay applied to repeat jobs between the same agent and buyer, the buyer-diversity factor, and the exact score formula, so any Proof Score can be reproduced independently. Free, read-only.

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

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?

Annotations already declare read-only, idempotent, non-destructive, and non-open-world behavior, so the safety profile is covered. The description adds that the call is free and that it returns both the methodology and its version, which is useful context beyond the structured annotations. It does not mention rate limits or auth needs, but those are less critical for a read-only documentation endpoint.

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?

The description is a single long sentence but is front-loaded with the core action and then structured as a list of methodology components. 'Free, read-only' partially repeats annotations but still earns its place by signaling cost and safety in one phrase. No significant waste, though it is denser than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, no output schema, and simple annotations, the description is complete enough for an agent to know exactly what it returns: the published methodology, its version, and the specific components included. Nothing required to invoke or interpret the call correctly is missing.

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 the baseline is 4. The description appropriately does not discuss parameters, and the empty schema is fully self-explanatory.

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 states a specific verb and resource: return the published Proof Score methodology and its version. It also enumerates what that methodology contains (inputs, decay rules, diversity factor, formula) so the agent knows exactly what this tool provides. It does not explicitly differentiate itself from sibling tools like proof_check or proof_verify_record, keeping it below 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?

The phrase 'so any Proof Score can be reproduced independently' implies the use case: retrieving the methodology to understand or reproduce scores. However, it gives no explicit when-to-use guidance relative to siblings such as proof_check or proof_verify_record, and no exclusions or alternatives are mentioned.

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