Skip to main content
Glama
Literature Evidence MCP

Literature Evidence MCP

by Furox-Art

rust_locate_quote

Opt-in Rust PyO3 literal quote match, no interpretation of scientific meaning.

Instructions

Opt-in Rust PyO3 literal quote match, no interpretation of scientific meaning.

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

Input Schema

NameRequiredDescriptionDefault
quoteYes
source_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

C2.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the key matching semantics (literal, no scientific interpretation), which tells an agent results will not be fuzzy or semantically inferred, but it says nothing about return content, behavior on no-match, or engine availability/failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence contains no filler, but it spends its limited words on 'Opt-in Rust PyO3' rather than front-loading the user-facing behavior, so brevity comes at the cost of clarity.

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

Completeness2/5

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

For a two-required-parameter tool with no output schema and no annotations, the description should say what a match returns (offset, span, boolean) and how source_text relates to quote. Neither is covered, leaving the agent guessing at the result shape.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and does not. 'quote' is only obliquely referenced and 'source_text' (the corpus to search) is never explained, nor is any format or case/whitespace sensitivity of the match.

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

Purpose3/5

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

It names the operation (literal quote match) and a differentiating trait (no interpretation of scientific meaning), but 'Opt-in Rust PyO3' is implementation jargon that does not tell an agent what the tool actually produces and it never mentions searching within source_text. It is distinguishable in spirit from verify_claim/nli_assess_evidence but not from verify_source_quote, which is an obvious near-sibling.

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

Usage Guidelines2/5

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

'Opt-in' hints that this is a non-default path, but there is no statement of when to choose it over verify_source_quote or verify_citation, no prerequisites, and no conditions under which it should not be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.