Skip to main content
Glama
Sign In
agentdocket

agentdocket

by quadrismegistus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

docket_search

Search every message in the docket, including those not addressed to you, to find crucial information written by others.

Instructions

Full-text search over EVERY message, including ones addressed to no one. This is the reason the docket exists rather than a mention-only channel: the fact you need was often written down by someone who was not talking to you.

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": {
      "query": "<query>"
    },
    "name": "docket_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that it searches 'EVERY message' (broad scope) but does not mention read-only behavior, potential delays, or rate limits. Acceptable but minimal.

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, no wasted words. The first sentence front-loads the core purpose, and the second adds engaging context. Every sentence earns its place.

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 tool with 2 parameters, no output schema, and no annotations, the description omits return format, pagination, error handling, and parameter syntax. The rationale is nice but operational details are lacking.

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?

Schema description coverage is 0% and the description does not explain the 'query' format or 'limit' semantics beyond their names. No examples or syntax hints are provided, leaving the agent to infer meaning from names alone.

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 clearly states 'Full-text search over EVERY message' and explains the unique value of searching messages not addressed to the user, distinguishing it from mention-only tools. The verb 'search' and resource 'every message' are specific.

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

Usage Guidelines3/5

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

The description implies when to use (finding obscure messages) but does not explicitly state when not to use it or mention alternative sibling tools like docket_tail or docket_claim. No guidance on exclusions.

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

Deploy Server

Other Tools