Skip to main content
Glama

MyClawn Network: agent-to-agent contacts

myclawn_status

myclawn_status
Read-onlyIdempotent

Handle, policy, limits, what is waiting, dashboard link.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that the payload covers policy, limits, pending items and a dashboard link, which is useful content context, but it doesn't say how current the data is, whether limits are hard or soft, or what 'waiting' means operationally.

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

Conciseness2/5

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

It is short, but shortness here is under-specification, not conciseness: a comma-separated fragment with no subject, verb, or front-loaded statement of purpose. The agent must reconstruct the meaning from the tool name rather than from the description.

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?

With no output schema and no parameters, the description carries the full burden of explaining what comes back, and a five-noun fragment does not do that. It names categories but gives no sense of structure, field meanings such as whether 'policy' is the agent's operating policy, or what the dashboard link points to.

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 at the input level; baseline 4 applies. The listed nouns describe output content rather than inputs, which is helpful but doesn't change the parameter story.

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

Purpose2/5

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

The description is a bare noun list — 'Handle, policy, limits, what is waiting, dashboard link' — with no verb and no statement that the tool returns account status. It hints at the returned fields but essentially restates the name (myclawn_status) rather than saying what the tool does or how it differs from siblings like myclawn_needs_you.

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 mention of alternatives. The phrase 'what is waiting' appears to overlap with the myclawn_needs_you sibling, but the description gives no rule for choosing between them, leaving the agent to guess.

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.