Skip to main content
Glama
Sign In
Avizo MCP Server

Avizo MCP Server

by songyb1998
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_demo_projects

Browse bundled Avizo and Amira demo projects (.hx files) with optional name filtering and result limits. Use to discover sample workflows for automation.

Instructions

List bundled Avizo .hx demo projects.

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": "list_demo_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
containsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided; description only states function without disclosing read-only nature, pagination, authentication needs, or other behavioral traits. Output schema exists but description doesn't leverage it.

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?

Extremely concise single sentence, front-loaded with verb and resource. Efficient but at the expense of important details.

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

Completeness2/5

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

For a tool with two optional parameters and output schema, the description should explain filtering behavior and return format. It omits both, leaving agents under-informed.

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

Parameters1/5

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

Parameter descriptions are absent from both schema (0% coverage) and description. The description does not explain 'limit' or 'contains' parameters, forcing reliance on parameter names and defaults alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses verb 'List' and specifies resource 'bundled Avizo .hx demo projects', clearly distinguishing it from sibling tools which focus on creation, execution, or inspection of scripts and projects.

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?

No guidance on when to use this tool versus alternatives like 'inventory_avizo_project' or when to use filtering parameters. Description lacks context for selection.

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

Deploy Server

Other Tools