Skip to main content
Glama

SCRIPTMASTERLABS — Agent Verify

Service status

service_status
Read-onlyIdempotent

Live service status with an as-of timestamp: ledger and verifier health, the ingest pipeline state, the Arc Merkle-anchoring state, and the status of each SML component the board probes. Check it before relying on records or scores if freshness matters. 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": "service_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond them by specifying that the data is a live snapshot carrying an as-of timestamp, and that calls are free — relevant context for a diagnostics endpoint.

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?

Two sentences, front-loaded with what is returned and followed by the actionable freshness caveat. The component list is dense but every item earns its place by telling the agent what surfaces the status covers.

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, the description carries the burden of describing return content, and it does so by listing the reported subsystems plus the as-of timestamp. It stops short of saying how degraded states are represented in the response, which is a minor remaining gap for a health check.

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 there is nothing for the description to disambiguate; baseline credit is warranted. The description correctly implies the call needs no arguments.

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 names a specific resource (live service status) and enumerates exactly which subsystems it reports on: ledger and verifier health, ingest pipeline, Arc Merkle-anchoring, and each probed SML component. That enumeration clearly separates it from siblings like ledger_list, proof_verify_record, and board_search, which read data rather than report health.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete triggering condition: check it before relying on records or scores if freshness matters. That is real when-to-use guidance tied to a decision, though it does not name an alternative tool or an explicit when-not-to-use case.

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