Skip to main content
Glama

Tresca

Look up a vendor's AI assistant

get_vendor_assistant
Read-onlyIdempotent

The AI assistants engineering software vendors build into their products (Autodesk Assistant, Bentley Copilot, Creo AI Assistant and others): status in each product in the vendor's own words, what it does, how it relates to MCP servers, and pricing as stated, with sources.

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": {
      "assistant": "<assistant>"
    },
    "name": "get_vendor_assistant"
  }
}

Input Schema

NameRequiredDescriptionDefault
assistantYesAssistant name, vendor or tool, e.g. "Autodesk Assistant", "Siemens", "Creo"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral framing: results are 'in the vendor's own words', 'as stated, with sources' — signalling verbatim, attributed vendor claims rather than verified fact. It does not state what happens on an unknown assistant, which is the main remaining gap.

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?

One dense but well-ordered sentence: resource definition and examples come first, then the returned facets, then the sourcing caveat. Every clause carries information, though the colon-list construction is slightly heavy for a single-parameter lookup.

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?

With an output schema, full parameter documentation, and complete annotations, the description only needs to frame scope and content, which it does. The gaps are the edge case of no matching assistant and the absence of alternatives guidance. Nothing about invocation itself is left unclear.

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 100% and the single parameter already documents that a name, vendor, or tool is acceptable, with the same example names the description uses. The description therefore adds little parameter meaning beyond the schema. Baseline 3 applies.

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 pins down a specific resource: AI assistants that engineering-software vendors embed in their products, with named examples (Autodesk Assistant, Bentley Copilot, Creo AI Assistant). It also enumerates the payload (status per product, function, MCP relationship, pricing, sources), which distinguishes it from siblings like get_tool or get_listing. It lacks an explicit verb such as 'retrieve' or 'look up', but the noun phrase is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use statement and no routing against the sibling tools (get_tool, get_listing, get_install_steps) that likely hold related vendor data. The agent must infer from the resource name alone whether this or get_tool is the right call. Only implicit guidance ('lookup by assistant name') is present.

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.