Skip to main content
Glama

signafAIde status

signafaide_status

API key and env, the service URL, each agent chain with its record count and last receipt, records waiting in the outbox, the quota, and the claim link with how long an unclaimed sandbox has left.

Instructions

API key and env, the service URL, each agent chain with its record count and last receipt, records waiting in the outbox, the quota, and the claim link with how long an unclaimed sandbox has left.

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

Input Schema

NameRequiredDescriptionDefault
directoryNoPath of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the returned status fields, but it does not state that the operation is read-only, whether it has side effects, or what permissions are needed.

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 definition is a single compact sentence with no filler, and the returned fields are listed efficiently. It could be more front-loaded with an explicit action verb, but it is not bloated.

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 appropriately compensates by listing the status fields an agent will receive. The optional directory parameter is covered by the schema, and the tool is simple enough that the remaining gap is mainly usage guidance rather than missing return-value context.

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

Parameters3/5

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

Schema description coverage is 100%, and the single optional 'directory' parameter is fully documented in the schema. The description adds no parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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 enumerates the status payload clearly: API key/env, service URL, agent chains, outbox records, quota, and claim link. It identifies the resource well, but it omits an explicit verb such as 'returns' and does not contrast itself with siblings like signafaide_claim_link or signafaide_verify.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no indication of when another sibling tool would be more appropriate. The agent must infer that this is a status/health inspection tool from the name and returned-field list alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.