Skip to main content
Glama

Margaret's poems

Search poems

search_poems
Read-onlyIdempotent

Keyword search over titles, tags and the poems themselves. Returns the best matches with a snippet; read one with get_poem.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesWords to look for, e.g. 'sky blue', 'moon', 'grief'
collectionNo'Singing in the Dark Times' (her 2022 book), 'Noun Poems', 'X' (poems posted on X), or 'new' (saved by hand, incl. commissions). Partial names work.

Output Schema

NameRequiredDescriptionDefault
hitsYes
countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / hits / items / properties / attested
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / hits / items / properties / commission
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / hits / items / properties / receipt_url
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety and idempotency are covered. The description adds that results are ranked ('best matches') with snippets, which is useful behavioral context not in the annotations. However, the output schema likely covers the return format, so the addition is modest.

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 tight sentences: the first defines scope, the second gives result semantics and the follow-up action. Every clause earns its place and the key information is front-loaded.

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?

Given an output schema exists (so return shape needn't be described), the description covers purpose, scope, result nature (snippet, ranked), and the recommended next step. It doesn't mention pagination or empty-result behavior, but for a read-only search tool this is largely complete.

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 coverage is 100%, so all three parameters (query, limit, collection) are documented in the schema, including examples for query and collection values. The description adds no parameter-level detail beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb (search) and resource (poems) and explicitly names the searched fields ('titles, tags and the poems themselves'). This distinguishes it from list_poems and random_poem among siblings.

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

Usage Guidelines4/5

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

Clearly states this is for keyword search and routes the agent to get_poem for reading a specific result. It doesn't explicitly say when NOT to use it (e.g., use list_poems for browsing), but the search/read distinction is clear.

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.

Resources