Skip to main content
Glama

Page through a checked brief

get_brief_results
Read-onlyIdempotent

Signed-in accounts only (a free account at https://syfert.com/mcp/; anonymous callers use check_brief with text). Read the results of check_brief(brief_id) one page at a time (each page under ~20k tokens). section: corrections (ranked by severity), cites (one full row per citation, as check_brief with detail="full"), quotes_unattached, statutes. Start without cursor, then pass next_cursor until it is null. After the last page of every section the session is deleted (session_deleted: true).

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": {
      "brief_id": "<brief_id>",
      "section": "<section>"
    },
    "name": "get_brief_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOmit for the first page; then the next_cursor of the previous page
sectionYesWhich section to read
brief_idYesThe brief_id brief_upload returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing page size (~20k tokens), section ordering (corrections ranked by severity), row shape for cites, the terminal condition, and the important side effect that the session is deleted after the last page of every section (session_deleted: true). That deletion is a lifecycle consequence of reading rather than a modification of user data, so it does not flatly contradict readOnlyHint=true, but the tension is worth stating explicitly as a warning rather than as a returned flag.

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?

Dense but every clause carries information — auth gating, pagination protocol, section semantics, deletion behavior. The only weakness is front-loading: the auth requirement occupies the opening position ahead of the tool's actual purpose, pushing the core verb into the second sentence.

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 names the key response fields (next_cursor, session_deleted) and explains the terminating condition, so an agent can loop correctly without guessing. Authentication prerequisites and page-size limits are also covered — nothing material is missing for a 3-parameter read tool.

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%, so baseline is 3, but the description adds real meaning: each section value is characterized (severity-ranked corrections, one full row per citation equivalent to detail="full", unattached quotes, statutes) and the cursor lifecycle is restated as first-page-omit then next_cursor. That is more than the enum labels alone convey.

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 and resource ('Read the results of check_brief(brief_id)') and scopes it to pagination ('one page at a time'), then enumerates the four sections. An agent can distinguish this from check_brief and from brief_delete/export_document without opening any 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 routing ('anonymous callers use check_brief with text') and an exact call protocol: 'Start without cursor, then pass next_cursor until it is null.' Both when-to-use and how-to-iterate are spelled out, with no inference required.

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