Skip to main content
Glama

native_read

Read-only

Extract calibrated native components, properties, and stored pin references directly from .pdsprj files without UI to inspect Proteus project data without running simulations.

Instructions

Read calibrated native components, properties and stored pin references directly from .pdsprj. No UI. Not simulation verification.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds that the read is direct from the .pdsprj file, has no UI component, and is not a simulation verification, but it does not cover failure behavior, output shape, or file-access constraints.

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 sentences/fragments, front-loaded with the operation and followed by scope qualifiers. No redundant prose; the telegraphic style is efficient though 'No UI' is terse.

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 one-parameter read-only tool with no output schema, the description identifies the source file and the classes of data returned. It still leaves the path argument and error/return-format behavior unspecified, so it is adequate but not fully complete.

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 only parameter (path) has no schema description (0% coverage), and the description never explains path syntax, relative vs absolute form, or required file extension. It only implies that the path points at a .pdsprj file, which is minimal compensation.

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?

States a specific verb ('Read') and the resources it returns—calibrated native components, properties, and stored pin references—and pins the source to .pdsprj. It does not name a sibling to use instead, but the source and 'not simulation verification' scope make it distinguishable from live/UI and verification tools.

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?

Provides clear source context ('directly from .pdsprj') and one explicit exclusion ('Not simulation verification'), which hints at when this is appropriate. It does not explicitly say when to choose it over native_inspect, native_check, project_read, or live_read, so routing still requires inference.

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