Skip to main content
Glama

Verify a quotation against the opinion

verify_quote
Read-onlyIdempotent

Check one quotation against the full text of the opinion it is attributed to, before it goes in quotation marks. Returns verdict (verbatim | near | absent), percent, best_match (the opinion's own sentence, up to ~600 characters), star_page (the last *page marker before it, null when the text carries none), offset (get_case offset), case and advice. near means the opinion says it in other words: paste matched_span (the opinion's words over the span you quoted) instead; best_match is the sentence around it. absent means the words are not in this opinion. Identify the case by cluster_id or reporter citation (case_name helps a citation newer than the reporter index). Quotation marks mean pasted from a tool result (opinion text, passage, best_match). If you typed a quote from memory, run verify_quote and use best_match. Run check_brief on the finished draft and apply its corrections. Copy cite_as for the citation (first page, then pin). A case_name alone also works: find_case decides, and a name that is not decisive returns candidates instead of an answer.

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": {
      "quote": "<quote>"
    },
    "name": "verify_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteYesThe quoted words exactly as you intend to use them (three or more words)
citationNoReporter citation of that case, e.g. "376 So. 2d 230" (used if cluster_id absent)
case_nameNoCase name; lets a citation newer than the reporter index resolve by name + date
cluster_idNoCluster id of the case the quote is attributed to
forum_stateNoOptional two-letter state code of the court you file in (il, ga, tx ... dc). Adds forum_cite to every case: the citation in the form that state's courts use for their own reports (other cases in Bluebook form), pinned where cite_as is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / forum_state
      Added value: +{
      +  "description": "Optional two-letter state code of the court you file in (il, ga, tx ... dc). Adds forum_cite to every case: the citation in the form that state's courts use for their own reports (other cases in Bluebook form), pinned where cite_as is.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-open-world, but the description still earns credit by disclosing the return shape in detail: verdict enum values with their meanings, percent, best_match capped at ~600 characters, star_page null semantics, offset as a get_case offset, and case/advice fields. There is no output schema, so this disclosure carries real weight; it loses a point only because truncation and matching tolerances behind "near" versus "verbatim" are not explained.

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 purpose, then verdict semantics, then case identification, then workflow — a sensible ordering with no filler. It is dense to the point of crowding several distinct concerns (return interpretation, house style for quotation marks, downstream tool routing) into one block, so a small amount could be trimmed or split.

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?

With no output schema and five parameters, the description fully compensates by enumerating the response fields and their interpretation, plus the case-resolution fallback behavior. Nothing an agent needs in order to call this correctly and act on the result 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 100%, so the baseline is 3, but the description adds resolution order beyond the schema: identify the case by cluster_id or reporter citation, case_name rescues a citation newer than the reporter index, and a bare case_name defers to find_case with a candidates fallback. Only forum_state goes unmentioned in prose, which the schema handles adequately.

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 specific verb and resource: "Check one quotation against the full text of the opinion it is attributed to." The scope is narrowed to a single quote (not a search of many), which separates it from the plural-quote sibling, and the triggering moment ("before it goes in quotation marks") makes the intent unmistakable.

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 when-to-use conditions plus routing: type-from-memory quotes go here and use best_match, while the finished draft goes to check_brief, and cite_as supplies the citation. It also states the downstream action for each verdict (paste matched_span for near, treat as absent otherwise), so the agent knows exactly what to do after calling.

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