Skip to main content
Glama

selftest

FREE, no payment required. Runs this agent's real capability on a fixed canned input and returns the genuine result, an honest assertion grade, and the full trust manifest (signed Agent Card, JWKS, governance/licence chain, safety posture) with a proof link for every claim. Intended for registries, graders and auditors: this is behavioural evidence, not a self-description.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the input is fixed/canned (implying determinism and no caller-supplied state), that the result is 'genuine', and it enumerates the artifacts returned including signed Agent Card, JWKS, governance/licence chain, and safety posture with proof links. It does not explicitly state side-effect or mutation behavior or latency/cost beyond 'FREE', which keeps it below a 5.

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?

Three sentences, front-loaded with the 'FREE' constraint and the core action, then the return payload, then the audience/purpose. The parenthetical manifest list is dense but earns its place by naming the concrete artifacts. Slight redundancy between 'honest assertion grade' and 'genuine result'.

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

Completeness4/5

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

With no output schema and no annotations, the description must explain return values itself, and it does: result, grade, and a trust manifest with per-claim proof links. For a zero-parameter, read-evidence tool this is close to complete; only side-effect guarantees and expected runtime/cost remain unstated.

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, which is the baseline-4 case. The description is consistent with that (fixed canned input, no caller configuration) and adds the useful implication that no arguments are needed or accepted.

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 uses a specific verb+resource framing: it 'runs this agent's real capability on a fixed canned input' and returns the result, an assertion grade, and a trust manifest. That is far more than a restatement of 'selftest'. It does not explicitly distinguish itself from the sibling 'invoke', so it stops 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?

It names an intended audience ('registries, graders and auditors') and frames the output as 'behavioural evidence, not a self-description', which implies when to reach for it. However, it never states when NOT to use it, nor contrasts it with the only sibling, 'invoke', which an agent would plausibly confuse it with.

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.