Skip to main content
Glama

live_read

Read-only

Reads current owned ISIS sheet components, physical pin numbers and names, transforms, and real wires, then returns a revision token for verified, non-screenshot schematic state.

Instructions

Read CURRENT owned ISIS sheet components, physical pin numbers/names, transforms and real wires. Returns revision token. No screenshots or input emulation.

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

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: it returns a revision token and does not do screenshots or input emulation. It does not state permission/auth requirements or how the revision token should be used.

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?

Three short, front-loaded sentences with no filler: capability first, return value second, exclusions last. Every clause carries information.

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?

For a one-parameter read tool with no output schema, the description adequately covers what is returned (components, pins, transforms, wires, revision token) and what is not. The only gap is that the session parameter is left unexplained.

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?

There is a single required parameter, 'session', with 0% schema description coverage, and the description never explains it. The name is largely self-explanatory, but no added meaning (format, lifetime, whether it must be an owned session) is supplied.

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?

Names a specific verb and a well-scoped resource: reading CURRENT owned ISIS sheet components, pin numbers/names, transforms and real wires. The word 'CURRENT' and 'owned' implicitly separate it from live_history and native_read, though it never names 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?

Usage is implied by 'CURRENT' (read live state) and by the exclusion 'No screenshots or input emulation', which signals this is not an interaction tool like live_edit. However, there is no explicit statement of when to prefer live_read over live_history, native_read or pcb_read.

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