Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

read_objects_result

Read-onlyIdempotent

Returns a retirement notice that redirects writes to edit({ text }) and reads to read({ paths }).

Instructions

Retired. A call answers the one line that names the door: edit({ text }) to write, read({ paths }) to read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_objects_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNo
pathsNo
queryNo
scopeNo
formatNo
blockIdNo
canvasIdNo
elementsNo
sessionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already carry the deprecation signal in the title ("Retired: use edit or read") plus readOnlyHint and idempotentHint, so the description's main added value is the concrete redirect to the replacement tools. It does not disclose the practical behavior of invoking a retired tool (error vs. no-op vs. stale result), which is the key unknown an agent has here.

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

Conciseness3/5

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

It is short and front-loads the retirement notice, which is good. However, the second clause is figuratively worded ("names the door") rather than plainly stating the replacements, costing clarity for no gain in length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a retired tool the essential facts are: don't call it, and call these instead — both are present, and no output schema is needed. What is missing is the failure mode of calling it and any note that the 9 schema parameters are vestigial, which leaves an agent guessing about the remaining surface.

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

Parameters2/5

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

The schema has 9 parameters at 0% description coverage, and the description supplies no meaning for any of them. The only parameter names it mentions (text, paths) belong to the suggested replacement tools, not to this tool's own schema, so an agent reading the description learns nothing about html, query, scope, blockId, canvasId, elements, or sessionId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what read_objects_result does or did; it only declares a status ("Retired") and redirects. It does successfully distinguish the tool from siblings by naming edit and read as replacements, but the purpose of the tool itself is left unstated and the phrasing "the one line that names the door" is opaque.

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 explicitly routes the agent: use edit({ text }) to write and read({ paths }) to read, which is exactly the when-to-use guidance an agent needs for a retired tool. It stops short of saying whether calling this tool still works or will error, so the guidance is clear but not exhaustive.

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