Skip to main content
Glama

Find cited text passages

get_text_passages
Read-onlyIdempotent

Find accent-insensitive passages of one literal phrase (quotes optional; words are not matched separately) in selected publication/video/podcast/chronicle IDs. Original UTF-16 offsets, bounded context, citations. Requires full text exposure.

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": {
      "ids": "<ids>",
      "keyword": "<keyword>"
    },
    "name": "get_text_passages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYespublication:, video:, podcast: or chronicle: ids
limitNoDefault 10, max 20
offsetNo
radiusNo
keywordYes

Output Schema

NameRequiredDescriptionDefault
countYes
offsetYes
resultsYes
has_moreYes
next_offsetNo
snapshot_idYes
unavailableNo
total_matchesYes
effective_limitNo
requested_limitNo
unavailable_idsYes
response_limitedNo
scanned_matches_cappedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ids / description
      Previous value: -"publication:, video: or podcast: ids"New value: +"publication:, video:, podcast: or chronicle: ids"
    • addedOutput schema / properties / unavailable
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "note": {
      +        "type": "string"
      +      },
      +      "reason": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "reason"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / results / items / additionalProperties
      Removed value: -false
  3. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  4. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior: accent-insensitive matching, single-literal-phrase semantics with no per-word matching, returned offsets in original UTF-16 units, bounded context, and citations. The access prerequisite is mentioned but not defined.

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?

Two dense, front-loaded sentences with essentially no filler; the matching constraint is stated before the access requirement. The telegraphic fragment style ('Original UTF-16 offsets, bounded context, citations.') is compact but slightly elliptical.

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?

An output schema exists, so enumerating return fields is optional and the brief mention of offsets/context/citations is a bonus rather than a gap. For a 5-parameter tool with a hard access prerequisite, the main remaining hole is what 'full text exposure' concretely means and what happens when it is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40% (limit and ids are documented; offset, radius, and keyword are not). The description partially compensates: it defines keyword as one literal phrase with optional quotes and no separate word matching, and 'bounded context' / 'Original UTF-16 offsets' gesture at radius and offset. Units for radius and the meaning of offset as an input remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Find') plus a specific resource ('passages') scoped to selected publication/video/podcast/chronicle IDs. The clause 'one literal phrase (quotes optional; words are not matched separately)' effectively distinguishes it from a general keyword search tool. It stops short of naming a sibling, so it sits at 4 rather than 5.

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

Usage Guidelines3/5

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

Gives one real precondition ('Requires full text exposure'), which tells the agent when the call will fail. However, it never says when to prefer this over search/fetch or what to do when full text is not exposed. Usage is implied rather than directed.

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.