SourceToMe

Retrieve source evidence

retrieve_evidence

Read-only

Return passages, edition, locator and provenance from the bounded public library. To request an exact indexed locator, provide one source ID and that full locator. Multiple IDs permit edition comparison; missing evidence is reported.

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": {
      "question": "<question>"
    },
    "name": "retrieve_evidence"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`locator`	No
`question`	Yes
`source_ids`	No

Output Schema

Name	Required	Default
`notice`	No	Public reference library. Lexical retrieval only. Source identity checks do not prove truth. This eBook is for the use of anyone anywhere in the United States and most other parts of the world at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org. If you are not located in the United States, you'll have to check the laws of the country where you are located before using this ebook. Full license: https://www.gutenberg.org/policy/license.html
`reason`	Yes
`status`	Yes
`coverage`	No	Insufficient
`evidence`	No
`error_code`	No
`limitations`	No
`independent_works`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed (openWorldHint=false) corpus, so the safety profile is covered. The description adds two genuine facts beyond that — the scope is a 'bounded public library' and missing evidence is reported rather than erroring — but nothing about volume or ranking behavior.

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?

Three dense sentences with the core purpose front-loaded and the two usage modes immediately after. Every clause carries information, though the locator sentence is packed tightly enough to need a second read.

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?

With an output schema present, return values need not be described, and the description covers purpose, the two invocation modes and the missing-evidence case. For a 4-parameter, 0%-coverage schema the undocumented 'question' and 'limit' parameters are the one remaining gap.

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 description coverage is 0%, so the description carries the full burden, and it supplies the non-obvious cross-parameter rule that a locator must be paired with exactly one source ID, plus the semantic effect of multiple source_ids. It leaves 'question' and 'limit' (default 5, max 5) entirely unexplained.

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 concrete verb+resource pair ('Return passages, edition, locator and provenance') and names the corpus it draws from ('bounded public library'). It is distinguishable from search_library and inspect_source in spirit, but never names or contrasts a sibling explicitly.

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

Usage Guidelines4/5

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

Gives real conditional guidance: one source ID plus a full locator retrieves an exact indexed locator, while multiple IDs switch the tool into edition-comparison mode. It stops short of stating when-not-to-use-this or naming search_library as the alternative for open-ended discovery.

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

All SourceToMe tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?