Skip to main content
Glama
Sign In

Sendora

by se.sendora
OverviewDiscussionsAdmin

Read a Sendora document

read_doc
Read-onlyIdempotent

Read one of Sendora's documents whole, as Markdown: a guide (sendora://docs/…), an API operation (sendora://reference/…), the error codes (sendora://errors) or an SDK's README and rules for agents (sendora://sdk/readme and sendora://sdk/skill for TypeScript, sendora://sdk/python/readme and sendora://sdk/python/skill for Python, sendora://sdk/php/readme and sendora://sdk/php/skill for PHP, and sendora://sdk/laravel/readme for Laravel). sendora://index lists every document; search_docs finds the right one.

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": {
      "uri": "<uri>"
    },
    "name": "read_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesA document's address, such as sendora://index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

While annotations handle safety hints, the description adds deep behavioral context by specifying the output format (Markdown) and detailing the exact URI schemes and naming conventions (e.g., sendora://sdk/python/skill for Python) that constitute a valid operation.

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?

The definition is extremely dense and uses a single, very long, highly structured sentence. While it achieves maximum information density, its run-on nature slightly detract from pure structural conciseness, though every piece of information is vital.

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?

Given that the tool relies entirely on external documentation addresses, this definition is maximally complete. It defines the scope of content, the input format, and its relationship to neighboring tools.

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

Parameters5/5

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

Although the schema is 100% complete, the description adds critical semantic meaning by defining the structure and scope of the accepted `uri` value. It is not just 'a string', but a specific Sendora URI following numerous defined patterns.

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 is highly specific, stating it reads documents 'whole, as Markdown'. It categorizes the content (guide, API, errors, SDK) and explicitly sets it apart from search_docs by indicating a URI must already be known.

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?

The description provides explicit guidance on when to use it—when a URI is known or predictable. It clearly directs the user to use search_docs when the URI is not yet known, establishing a clear workflow boundary.

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

All Sendora toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources