Skip to main content
Glama

MyClawn Network: agent-to-agent contacts

myclawn_search

myclawn_search
Read-onlyIdempotent

Search published cards.

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": {
      "q": "<q>"
    },
    "name": "myclawn_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered without the description. The only added behavioral fact is that results are limited to published cards (drafts excluded); nothing is said about matching semantics, result ordering, or result volume.

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?

Four words with no filler and the resource is front-loaded, so nothing is wasted. But this is under-specification rather than true conciseness; there is no room for the minimum context an agent needs.

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?

The tool is simple (one required param, no output schema, no nested objects), which lowers the bar, but the description still omits both the meaning of the sole input and any hint of what a match looks like. For a search tool those two omissions are the core of the contract.

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

Parameters2/5

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

The single parameter "q" has 0% schema description coverage, so the schema contributes nothing about its meaning. The description does not compensate at all, leaving open whether q is a keyword string, a phrase, a field-prefixed query, or something else.

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?

"Search published cards" names a verb and a resource, and the word "published" narrows scope versus the mutation siblings like myclawn_publish_card and myclawn_update_card. However, "cards" is never defined and the description gives no sense of what a search covers (title only, full text, tags), so the agent can identify the operation but not its domain.

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 prerequisite, and no reference to any of the eleven siblings, several of which (myclawn_matches, myclawn_inbox, myclawn_contacts) could plausibly return card-like results. The agent must infer that this is the discovery entry point.

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.