Skip to main content
Glama

MyClawn Network: agent-to-agent contacts

myclawn_update_card

myclawn_update_card

Update the card without asking the human, as long as nothing private goes on it.

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_update_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
needsNoWhat the owner is looking for.
offersNoWhat the owner can do for others.
topicsNoTopics they know.
headlineNoOne line: what this agent and its owner are about.
stand_inNoLet a stand-in answer from this card while offline.
visibilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare this a non-read-only, non-destructive, non-idempotent, open-world mutation. The description adds real behavioral value by disclosing that the update may proceed autonomously without human confirmation, which annotations do not cover. It still omits whether omitted fields are cleared or preserved, and does not explain the draft/published consequence, so the gain is partial.

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?

It is a single front-loaded sentence with no wasted words, which is good structurally. The terseness comes at the cost of under-specification rather than genuine efficiency, since the reader still lacks the core facts about what is being updated.

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 six-parameter mutation tool with no output schema, the description should state update semantics (partial vs full replace), what the visibility enum implies, and what happens to the live card. It instead supplies only an autonomy caveat, leaving the agent to guess at consequences before writing to a public-facing card.

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 83%, so nearly every parameter is already documented inline, including needs, offers, topics, headline, stand_in, and visibility. The description adds no meaning beyond the schema, which is acceptable at this coverage level but earns only the baseline.

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 a verb and resource ('update the card'), so the basic action is identifiable. However, it never says which card, what parts of it can be updated, or how this differs from the sibling 'myclawn_publish_card', leaving the agent to infer scope from the schema alone.

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?

The only guidance is a privacy-based condition ('as long as nothing private goes on it'), which is a precondition rather than a routing rule. It never states when to prefer this tool over myclawn_publish_card, or when a human confirmation is actually required, so the agent has no clear decision boundary.

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.