Skip to main content
Glama

Tresca

Search MCP servers and agent skills for engineering software

search_listings
Read-onlyIdempotent

Search Tresca's MCP servers, agent skills and plugins for engineering software by text, or browse by tool, discipline or AI client; filter by type, official, operating system and whether it can change models. Returns the facts that decide a choice and each listing's Tresca page. Order: official first, then most recently updated (with a query, best matches first); never a ranking. Words like 'best' or 'MCP' are ignored; if no listing matches every word, listings matching some of them are returned with a note. Needs a query, tool, discipline, client, or official: true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoOperating system it runs on
toolNoTool slug or name, e.g. "autocad", "Ansys Mechanical", "civil3d"
typeNoOnly MCP servers, agent skills or plugins
limitNoResults per page, 1-25 (default 10)
queryNoWords to search for, e.g. "revit", "plaxis python", "kicad drc"
accessNoWhether it can change models or files
clientNoAI client named in the project's docs, e.g. "Claude Code", "Cursor"
cursorNonextCursor from the previous page
officialNotrue: only listings the software's vendor publishes
disciplineNoDiscipline slug or slugs from list_disciplines, e.g. "geotechnical-engineering", or ["fea-simulation", "cfd"]; "simulation" covers both

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds substantive behavior: result ordering (official first, then most recently updated, best matches when a query is present), an explicit 'never a ranking' disclaimer, stop-word handling, and a partial-match fallback with a note. What remains unstated is pagination mechanics beyond the cursor param.

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?

Purpose is front-loaded and every clause carries information — no filler sentences. The semicolon-chained packing makes it denser than ideal to scan, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Ten parameters, all schema-documented, plus an output schema, so return-value detail is not required — yet the description still summarizes what comes back (decision facts plus each listing's Tresca page). Ordering, fallback behavior, and the at-least-one-input requirement close the gaps an agent would otherwise hit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above that by adding the cross-parameter rule that at least one of query/tool/discipline/client/official must be supplied, and by explaining that words like 'best' or 'MCP' are stripped from query. The remaining filter parameters are only restated at enum level, which the schema already does.

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?

Opens with a specific verb and resource: 'Search Tresca's MCP servers, agent skills and plugins for engineering software by text, or browse by tool, discipline or AI client.' It also names the filter dimensions, so an agent knows exactly what the tool covers. It stops short of explicitly contrasting itself with the get-by-id siblings (get_listing, get_tool), which keeps it out of the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real invocation precondition — 'Needs a query, tool, discipline, client, or official: true' — which is essential because the schema marks zero required parameters. It also distinguishes text search from browsing by tool/discipline/client. It does not name alternatives for when a known listing should be fetched directly instead.

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.