Skip to main content
Glama
Sign In
OpenXE MCP Server

OpenXE MCP Server

by Avatarsia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

openxe-discover

Read-onlyIdempotent

Lists available OpenXE actions at conversation start. Optionally filter by category to narrow results.

Instructions

Shows available OpenXE actions. Call ONCE at conversation start, then use 'openxe' tool to execute actions. Do NOT call more than once per conversation. Optional: category filter.

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": "openxe-discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoKategorie-Filter (default: alle)alle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the behavioral constraint of calling only once per conversation, which is valuable context beyond the annotations. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences long, front-loaded with the core purpose, and wastes no words. Every sentence adds value: purpose, usage frequency, sibling reference, and parameter note.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is nearly complete. It could mention that the output is a list of available actions, but the purpose implies that. The guidance on when to call and the sibling reference are sufficient for an agent to use the tool correctly.

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% and the parameter 'category' is already fully described with enum values and default. The description only mentions an optional category filter without adding new meaning, so it meets the baseline but does not exceed.

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 tool shows available OpenXE actions and specifies when to call it (once at conversation start). It distinguishes itself from the sibling 'openxe' tool by indicating that 'openxe' is for executing actions, making the purpose very clear.

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

Usage Guidelines5/5

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

The description explicitly provides usage guidance: call once at conversation start, do not call more than once, and use the sibling 'openxe' tool for execution. This leaves no ambiguity about when and how to use this tool.

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