Skip to main content
Glama

Default-watch and pinning service

probe

Session-start probe: reconcile the effective default against changelog state -> verdict + signed attestation

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": {
      "platform_id": "<platform_id>",
      "effective_model": "<effective_model>"
    },
    "name": "probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
platform_idYes
effective_modelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It indicates that a verdict and signed attestation are produced, but it does not disclose whether the probe mutates state, what permissions are required, how mismatches are handled, or whether the attestation is created or merely returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with the session-start context front-loaded. However, the arrow notation and dense jargon make it cryptic rather than efficiently informative, so conciseness comes at the cost of clarity.

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

Completeness2/5

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

For a tool with two required parameters, no annotations, no output schema, and 0% schema description coverage, this description is far too sparse. It hints at output values but omits parameter meaning, safety profile, error behavior, and how it relates to the attestation and changelog siblings.

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

Parameters1/5

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

Schema description coverage is 0%, and the description never mentions the required parameters platform_id or effective_model. The phrase 'effective default' vaguely gestures at effective_model, but an agent gets no format, meaning, or constraint information for either parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an action ('reconcile') and an output ('verdict + signed attestation'), but the resource is obscured by jargon like 'effective default' and 'changelog state'. It hints at a session-start verification flow but does not clearly distinguish itself from siblings like verify_attestation or delta_run.

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 'Session-start probe' implies a timing context, but there is no explicit guidance on when to use this tool versus verify_attestation, delta_run, or ingest_changelog. No exclusions or prerequisites are stated.

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