Skip to main content
Glama

effectsize

Read cases

get_cards
Read-only

Read up to 5 cases found by search_cases. Pick sections to save context: problem, solution, tools, core_idea, how_to_apply, code, results, limitations, talk (full edited transcript of a talk, paged with offset). Default: problem, solution, core_idea, results, limitations (~1k tokens per card); ask for how_to_apply / code when the user is going to implement. Open about 3 cards per call; the response is capped by max_tokens (default 5000). Every card also returns materials: the original (url, format, language, access: open | video | paywall | bot-blocked | offline, with a note on how to get it), the transcript if there is one, code repositories, slides and other extras. Use them as described in the server instructions; ask the user to fetch an original you cannot access.

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": {
      "slugs": "<slugs>"
    },
    "name": "get_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYesCase slugs from search_cases results (the `slug` field).
offsetNoCharacter offset for the talk section.
sectionsNoCard sections to return; default: problem, solution, core_idea, results, limitations. 'talk' = full transcript, paged with offset.
search_idNosearch_id of the search these cases came from (for logging relevance).
max_tokensNoApproximate cap on the response size; long sections are truncated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that: context cost (~1k tokens per card), a 5000-token default response cap with truncation of long sections, talk-section paging via offset, and an access taxonomy for materials (open/video/paywall/bot-blocked/offline) with a fallback instruction. This is exactly the kind of budget and failure-mode disclosure annotations cannot carry.

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?

Front-loaded with the core action, then progressively detailed guidance, and essentially every sentence carries actionable information for a token-budget-sensitive tool. It is dense with parentheticals and the line break mid-sentence is awkward, but there is no filler to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description covers the return shape (per-card sections plus a materials block with url/format/language/access, transcripts, repos, slides) and the truncation behavior. For a read tool with a fully documented 5-param schema, nothing an agent needs to call it correctly is missing.

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 already 100%, so the baseline is 3; the description still adds practical meaning by restating the default section set, quantifying what max_tokens costs per card, and framing offset as paging for the talk transcript. It does not, however, explain search_id's role (logging relevance) beyond what the schema says.

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?

Opens with a concrete verb+resource+limit: 'Read up to 5 cases found by search_cases.' It immediately establishes the read nature and the relationship to the sibling search tool, and the following sentence enumerates exactly what a 'case' contains, so an agent knows what it is getting without opening the 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?

Gives explicit operating guidance: default section set, when to request how_to_apply/code ('when the user is going to implement'), how many cards per call (~3), the max_tokens cap, and how to handle materials the server cannot access (ask the user to fetch the original). It also points to server instructions for materials usage rather than duplicating them.

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.