Skip to main content
Glama
Sign In
Avizo MCP Server

Avizo MCP Server

by songyb1998
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_hx_scripts

List .hx scripts in a project tree, with optional filtering by content and a configurable limit, returning basic metadata.

Instructions

List .hx scripts in a project tree with basic metadata.

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": {
      "root_path": "<root_path>"
    },
    "name": "list_hx_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
root_pathYes
containsNo
limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It only states the tool lists scripts with metadata but does not disclose side effects, permission requirements, or whether it's a read-only operation. Key behavioral traits are missing.

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 description is a single sentence, which is concise, but it sacrifices necessary detail. It could include a bit more context without becoming verbose.

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?

Given three parameters and an output schema, the description is incomplete. It does not explain what 'basic metadata' entails or what the output looks like. This inadequacy hinders effective tool selection and usage.

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?

The description adds no meaning beyond the parameter names in the schema. With 0% schema description coverage, the agent gets no explanation of what `contains` filters or how `limit` works, leaving ambiguity.

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?

The description clearly states the action (list), the resource (`.hx` scripts), and the scope (in a project tree). It effectively distinguishes from sibling tools like `create_hx_script` and `inspect_hx_script`.

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?

The description provides no guidance on when to use this tool versus alternatives. It lacks context such as prerequisites, alternatives, or typical use cases, leaving the agent to infer usage.

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