Skip to main content
Glama
Sign In

Agent Wikis

by io.github.tonbistudio
OverviewDiscussionsAdmin

Read an agent tool

read_agent_tool
Read-onlyIdempotent

Load one agent tool by name. A "pro" (read-only) tool: its README (what it checks, how to run it) plus its file list. Add path to read one listed file, e.g. the source. The tool runs on the user's machine, not here. Before saving, running or scheduling anything from it, show the user what it does and get their explicit OK. Each file comes with its sha256. For a "download" tool you get its README and a download link (valid 15 minutes) with the archive's sha256 instead. Needs a Pro key; without one you get the summary and how to unlock it.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTool name from list_agent_tools, e.g. "copy-lint".
pathNoOptional file within the tool, as listed by read_agent_tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses that execution happens on the user's machine, not the server, and that a Pro key is required, with unauthenticated callers receiving only a summary. It also covers return details such as per-file sha256 hashes and, for download tools, a README plus a 15-minute download link with the archive hash.

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 front-loaded with the core action and stays dense with relevant facts, but some sentences pack multiple ideas into parentheticals, making it slightly harder to scan than it could be. No sentence is wasted.

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?

For a two-parameter read tool with no output schema, the description covers what is returned (README, file list, hashes, download link), the environment where it runs, the licensing gate, and the user-approval safety step. An agent has everything needed to call it and interpret the result correctly.

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 100%, so both parameters are already documented. The description adds a workflow meaning beyond the schema by explaining that path reads one file from the listed set, for example the source, which helps an agent choose between the two request modes.

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 states a specific verb and resource ("Load one agent tool by name") and ties it to the sibling workflow by noting the name comes from list_agent_tools. It also distinguishes the two request modes: a README plus file list, or a single file when path is supplied.

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?

The description gives clear context for using it: fetch a tool, then add path to read one listed file such as the source. It also sets a strong prerequisite behavior, requiring explicit user approval before saving, running, or scheduling anything from the tool. It does not name alternative sibling readers, though the other read_* tools cover different resources.

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

All Agent Wikis 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