Skip to main content
Glama

native_inspect

Read-only

Reads .pdsprj ZIP contents and hashes for inspection purposes, without claiming electrical verification. Use it to inspect Proteus project files and confirm their contents.

Instructions

Read .pdsprj ZIP contents and hashes. Does NOT claim electrical 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_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered without the description. The description's added value is the explicit scope boundary that it makes no electrical-verification claim, but it never says what the hashes cover, which algorithm, or whether the archive is fully parsed or only listed.

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

Conciseness4/5

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

Two short sentences, front-loaded with the action before the scope disclaimer, with no filler. The wording is terse to the point that the second sentence reads as a fragment, but nothing is wasted.

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?

With no output schema and no documented parameter, the description must carry more weight than it does: the return shape (file list plus hash values) and path expectations are left unstated. Adequate to pick the tool over a verification tool, insufficient to call it confidently.

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?

One required parameter 'path' has 0% schema description coverage, and the description says nothing about it — no format, no expectation of an absolute path vs. workspace-relative, no .pdsprj extension requirement. The single parameter an agent must supply is entirely unexplained in prose.

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 concrete verb and resource: reads .pdsprj ZIP contents and hashes. This is distinguishable from a plain project read, though it never clarifies whether 'contents' means a file listing, extracted members, or a summary, and it never names native_read or native_check as neighbors.

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 only implied through the negated scope 'Does NOT claim electrical verification', which hints verification belongs to another tool but never says which one or under what conditions to call this instead. No prerequisite or when-not guidance beyond that single exclusion.

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