Skip to main content
Glama

arsaze-mcp

by io.github.AnrosPrac
OverviewDiscussionsAdmin

arsaze_tools

Read-onlyIdempotent

Arsaze's tool catalogue — served on demand instead of loaded up front.

No arguments: every tool name, grouped by domain (a table of contents).
names=[...]: exact signatures + parameter docs for those tools — do this before the first arsaze_call to a tool.
query='split a clip': the best-matching tools — and workspace files, for reads — best first.
Signatures read `param?: type` for optional params. Reads are not tools — they're files (ws_ls).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namesNo
queryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable behavioral context: on-demand serving, mode-dependent outputs, and the specific note that reads are not tools but files (ws_ls). This goes beyond annotation basics without contradiction.

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 compact and well-structured, with each mode on its own line and the key fact (on-demand catalogue) front-loaded. Every sentence adds necessary information with no fluff.

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 output schema exists, the description reasonably covers invocation modes and expected outcomes. The only notable gap is that it doesn't clarify whether names and query can be used together, which could confuse an agent. Overall it is nearly complete for a quick-reference tool.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully compensate. It does: it explains the no-argument default, names mode returning signatures/param docs, query mode returning best-matching tools, and the `param?: type` optional-param notation. This is far beyond the bare schema.

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 identifies this as an on-demand tool catalogue with three explicit modes: no arguments for a table of contents, names for signatures, and query for best-matching tools. It differentiates itself from operational siblings like arsaze_call and ws_ls by being a discovery/metadata tool, not an action tool.

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?

It gives explicit context: use names before the first arsaze_call, use query for matching, and it distinguishes reads as files handled by ws_ls. However, it doesn't explicitly state when not to use this tool versus other siblings beyond reads, and it leaves the relationship between names and query (mutually exclusive vs combinable) unstated.

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

All arsaze-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources