Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

lookup

Read-onlyIdempotent

Returns the one line that names the door to the correct canvas operation: edit to write, read to read. Retired; call edit and read directly.

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": "lookup"
  }
}

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

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and carry the title 'Retired: use edit or read'. The description repeats both facts (retirement and the edit/read routing) without adding any behavioral context such as whether existing callers still work, whether calls error or no-op, or what happens to in-flight usage. It is consistent with the annotations but contributes almost nothing beyond them.

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?

The two sentences are brief and the deprecation notice is correctly front-loaded. The middle clause, 'A call answers the one line that names the door,' is ornamental wording that consumes space without conveying anything an agent can act on.

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 this, call edit or read — is present, which is the main thing an agent needs. It is incomplete in that a 9-parameter schema is left entirely unmapped, so an agent holding existing lookup-style arguments has no guidance on translating them to the replacement tools.

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?

There are 9 parameters with 0% schema description coverage, so the description carries the full explanatory burden and fails to meet it. It hints that text belongs to edit and paths to read, but says nothing about query, scope, format, blockId, canvasId, elements, or sessionId. The retirement framing mitigates this, but per the coverage rule the description does not compensate for the gap.

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 opening word 'Retired' tells the agent the tool is defunct, and the sentence names edit and read as replacements, which does differentiate it from siblings. However, the description never says what lookup itself does or did, and 'A call answers the one line that names the door' is opaque rather than clarifying. An agent knows to avoid it, but not what it was for.

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 routing instruction is explicit: use edit({ text }) to write and read({ paths }) to read, which maps the two core intents to concrete alternatives. It stops short of covering the other parameter concepts in the schema (query, canvasId, elements, sessionId), so an agent with a non-text, non-path use case gets no direction, but for a retired tool this is largely adequate.

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