Skip to main content
Glama
Sign In

Easy Scribe

by guide.easyscribe
OverviewDiscussionsAdmin

Get a document

get_document
Read-only

Returns a document's status and, once completed, its full content with screenshot links that stay valid for 24 hours. Content is Markdown when unedited and HTML after edits in Easy Scribe.

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": {
      "document_id": "<document_id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesThe document_id from create_document or list_documents.
include_contentNoDefault true. Set false to check status only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safe-read profile, and the description adds real value beyond that: screenshot links expire after 24 hours, and content format shifts from Markdown to HTML after Easy Scribe edits. It does not state what happens to content while status is still pending.

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 dense sentences, front-loaded with the return contract and with zero filler. The 24-hour expiry and Markdown/HTML caveat are exactly the details an agent would otherwise have to discover by trial.

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 no output schema, the description carries return-value disclosure and does so well: status, content, screenshot links, and format rules. It stops short of enumerating status values or the null/pending content case, which an agent deciding whether to re-poll would want.

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 100% and both parameters are documented there, so the baseline is 3. The description's "once completed" hints at the status-only mode toggled by include_content but adds no format or default detail the schema lacks.

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?

The description names the specific verb-resource pair (returns a document) and enumerates what comes back: status, content, and screenshot links. It is clearly a single-document read, distinct from list_documents or create_document, though it does not name those siblings explicitly.

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?

"Once completed" implies this is the polling tool after create_document, but the description never says when to use it versus list_documents or when to stop polling. Usage is only inferable from the schema note about where document_id comes from.

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

All Easy Scribe toolsInspect
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