Skip to main content
Glama

project_validate

Read-only

Validates a Proteus project by checking model pin existence, MCU supplies/reset, and floating passive pins; use it for targeted design checks, not full ERC.

Instructions

Check model pin existence, MCU supplies/reset and floating passive pins. NOT full ERC.

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": {
      "project": "<project>"
    },
    "name": "project_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 structurally. The description adds genuine value by disclosing the limited diagnostic scope, but says nothing about what a failing check looks like, whether it mutates project state, or how results are reported.

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 compact sentences with the scope statement front-loaded and the exclusion immediately following it; nothing is wasted, though the terseness leaves the first clause somewhat opaque.

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 single-parameter read-only validation tool with no output schema, the description conveys the enough-to-call essentials and the scope boundary. It is somewhat thin on what the returned diagnostics look like, but the annotation and schema burden is low.

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?

Schema description coverage is 0% and the single 'project' parameter is never mentioned in the description. The parameter is nonetheless self-explanatory given the project_* sibling family, so the gap is small but real.

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?

The description names a specific verb ('Check') and enumerates the concrete checks performed: model pin existence, MCU supplies/reset, and floating passive pins. The 'NOT full ERC' clause sharply bounds the scope, though the phrase 'model pin existence' is slightly jargon-heavy and no sibling alternative is named.

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?

The negative guidance ('NOT full ERC') tells the agent this is a lightweight subset check, which implicitly signals when it is insufficient, but there is no positive statement of when to run it (before export? before firmware build?) and no named alternative for full electrical rule checking.

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