Candidate Falcon

Read CandidateFalcon free material

read_free_material

Read-onlyIdempotent

Returns the text of one public CandidateFalcon material by the ID from search_free_materials, with its title and source URL. Long texts are paginated by character offset (limit up to 12,000 characters); nextOffset is null on the last page.

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": {
      "id": "<id>"
    },
    "name": "read_free_material"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	ID returned by search_free_materials.
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`nextOffset`	Yes
`totalCharacters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/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 real behavioral context beyond them: long texts are paginated by character offset, the limit caps at 12,000 characters, and nextOffset is null on the final page. It could additionally note what an invalid or private ID returns, but the pagination contract is well disclosed.

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

Conciseness5/5

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

Two sentences, both front-loaded: the first states what is returned and the required ID provenance, the second states the pagination contract. No filler and no restatement of the title.

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, the description needn't enumerate return fields, and it correctly focuses on the pagination behavior an agent must know to iterate pages. For a simple 3-parameter read tool with rich annotations this is close to complete, missing only error/empty-result behavior.

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 only 33% (only 'id' is described in the schema), so the description must carry the other two parameters, and it does: it explains that pagination is by character offset, that limit caps at 12,000 characters, and that nextOffset null signals the last page. That gives usable meaning to limit and offset beyond their bare integer types.

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?

The description uses a specific verb and resource ('Returns the text of one public CandidateFalcon material') and scopes it precisely by ID. It also names the sibling tool that produces the required ID, so an agent can distinguish this from search_free_materials without opening either schema.

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?

It clearly implies the usage context by stating the ID comes 'from search_free_materials', which effectively routes the agent to the search tool first and then to this read tool. It does not state any exclusion conditions or failure behavior for unknown IDs, so it stops short of full when/when-not guidance.

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

All Candidate Falcon 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?