Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

objects_result

Read-onlyIdempotent

Returns the retired-tool pointer that names the correct call: use edit({ text }) to write content or read({ paths }) to read it.

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": "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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and title it 'Retired', so the description's 'Retired' opener mostly repeats structured data. It adds the actionable next step (which sibling to call), which is real value, but says nothing about what happens if the tool is still invoked.

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?

'Retired.' is front-loaded and efficient, which is the right structure for a deprecation notice. The second sentence is needlessly cryptic ('the one line that names the door') and could have been a plain 'Use edit to write and read to read.'

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 with no output schema, the essential message (do not call; call these instead) is present. However, the redirect is only partially credible against nine undocumented parameters, and the description never confirms whether calls still succeed or error out.

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?

Nine parameters at 0% schema description coverage, and the description documents none of them. Because the tool is retired the omission matters less, but an agent reading the schema gets no help understanding html, paths, 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 opens with 'Retired', which tells an agent the tool's status, but it never states what objects_result actually does or returns. The redirect to edit/read is concrete, so the agent knows where to go, but the resource itself remains unnamed.

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?

Explicitly routes the agent to alternatives: 'edit({ text }) to write, read({ paths }) to read.' The mapping of intent to sibling is clear, though the surrounding phrase 'answers the one line that names the door' is obscure and adds ambiguity rather than context.

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