Skip to main content
Glama

Tresca

Look up an engineering tool

get_tool
Read-onlyIdempotent

Is there an MCP server or agent skill for an engineering tool (e.g. AutoCAD, Revit, ANSYS, KiCad, PLAXIS), and is one official? Returns counts, official listings, the vendor's AI assistant and its status, scripting interfaces with documentation links, and the tool's Tresca page. If the name could mean several tools (e.g. 'ansys') or isn't on Tresca, returns found: false with suggestions to call again with.

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": {
      "tool": "<tool>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool slug, name or other name, e.g. "revit", "SOLIDWORKS", "fusion 360"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds genuinely new behavior — that ambiguous or unknown names return found: false with suggestions rather than an error. It also discloses the payload shape (counts, official flag, vendor assistant status, scripting docs, Tresca page). The closing sentence is truncated ('call again with.') which blunts the retry instructions.

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 opening question is well front-loaded and the return-value enumeration is dense with no filler. However, the second sentence is a long comma-chained list and the final clause is cut off mid-thought, leaving the retry guidance incomplete. Efficient in intent, sloppy in execution.

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?

An output schema exists, so return values need no elaboration, yet the description still outlines the payload and the found: false path, which is the piece an agent most needs for planning. With one fully documented parameter and covering annotations, the only real omission is guidance on what to do next when suggestions come back. Sufficient for a low-complexity lookup tool.

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 coverage is 100% for the single 'tool' parameter, and the schema already gives examples and length bounds. The description adds only the notion that alternate names/spellings and ambiguous short names are accepted, which is mildly useful but thin. Baseline 3 applies where the schema does the heavy lifting.

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 poses a concrete question — does an official MCP server or agent skill exist for a named engineering tool — and enumerates what comes back (counts, official listings, vendor AI assistant status, scripting interfaces, Tresca page). The domain is unmistakable and concrete examples (AutoCAD, Revit, ANSYS, KiCad, PLAXIS) pin it down. It stops short of naming how it differs from siblings like get_listing or search_listings, so it is clear but not sibling-differentiated.

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 context is implied by the question framing — you call this to check availability/officialdom of a tool — and the ambiguous-name case ('ansys') hints at single-tool lookup semantics. There is no explicit when-to-use versus when-not, and no pointer to get_listing or search_listings for the follow-up cases the description itself raises. Guidance is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.