Skip to main content
Glama
Sign In

PoemShip

by com.poemship
OverviewDiscussionsAdmin

List collections

list_collections
Read-onlyIdempotent

For an occasion or a feeling (a wedding, a funeral, missing someone, autumn), the library's collections of poems in a language (all languages when none is given): title, slug, a short introduction and the link. Pick the closest and call get_collection with its slug. Collections exist in English, Russian and Belarusian.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the poems, an ISO 639-1 code: en, ru, be, de, fr, es, it, pl, nl, sv, da, nb or uk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, closed-world read, so the description does not need to restate safety. It adds value by disclosing the four fields returned per collection and by positioning the tool as a discovery step that precedes get_collection. It does not discuss result volume or paging, which is the main remaining unknown.

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

Conciseness4/5

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

Three dense sentences, front-loaded with the intent condition and ending with the handoff action; nothing is padding. The first sentence is an awkward fragment with a long parenthetical and colon list, which costs a little readability but not substance.

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?

For a one-parameter, read-only discovery tool with no output schema, the description covers intent, default behavior, returned fields and the next call — essentially everything needed. The one gap is the mismatch between the stated three available languages and the twelve-value enum, which could make an agent request a language that yields nothing.

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?

Schema coverage is 100% and the enum already documents the ISO codes, so the baseline is 3. The description goes beyond the schema by stating the default when no language is supplied and by narrowing the effective coverage to English, Russian and Belarusian — useful semantics, though that claim conflicts with the twelve-language enum and may mislead an agent about which codes return results.

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 names a specific verb and resource (lists the library's collections of poems) and states the organizing axis — occasion or feeling — with concrete examples (wedding, funeral, missing someone, autumn). It also tells the agent what each item contains (title, slug, short introduction, link), so the return shape is inferable without an output schema.

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

Usage Guidelines5/5

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

It gives an explicit entry condition (when the user has an occasion or feeling rather than a known poem or poet) and an explicit follow-up route: pick the closest collection and call get_collection with its slug. The meaning of omitting the parameter is also stated ('all languages when none is given'), so an agent knows the unfiltered case is valid.

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

All PoemShip toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources