Retrieve the content of selected spans within a session to access specific text chunks for processing.
Retrieve the content of one or more spans. Enforces max_chars_per_response.
Args: session_id: Session containing spans span_ids: List of span IDs to retrieve
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | ||
| span_ids | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description mentions max_chars_per_response but omits other behavioral details like idempotency, side effects, or error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Short and front-loaded purpose. The args section is integrated, no wasted sentences.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple tool. Output schema exists, so return value not required. But could elaborate on max_chars_per_response behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Description adds brief meaning for each parameter beyond schema titles, compensating for 0% schema coverage. However, it does not elaborate on format or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it retrieves span content, with a constraint on max characters. Distinguishable from siblings like rlm.artifact.get, though 'spans' assumed understood.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs alternatives. The sibling list exists but description does not differentiate usage scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrianwedd/rlm-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server