Skip to main content
Glama
Sign In
Arachne MCP Server

Arachne MCP Server

by Samuelfmedeiros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

arachne_capabilities

Retrieve the complete list of capabilities, engines, and recommended tools available in the Arachne platform for immediate understanding of server functionality.

Instructions

Auto-discover all capabilities, engines, and recommended tools of the Arachne platform.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It states the tool 'auto-discovers' but does not disclose whether it is read-only, has side effects, or requires authentication. For a tool with no parameters and a simple purpose, the description is adequate but lacks explicit behavioral traits.

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 consists of one concise sentence that is front-loaded and contains no wasted words. It efficiently communicates the tool's core function.

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 (no parameters, no output schema, no annotations), the description is nearly complete. It could be improved by noting the format or nature of the output, but for a discovery tool, the provided description is sufficient to inform an agent.

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

Parameters4/5

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

The tool has zero parameters, so schema description coverage is 100% trivially. Baseline is 4 per rules. The description adds no parameter information because none is needed.

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 clearly states the tool auto-discovers all capabilities, engines, and recommended tools of the Arachne platform. It uses a specific verb ('discover') and defines the resource scope, effectively distinguishing it from sibling tools that perform concrete actions like extraction or search.

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

Usage Guidelines3/5

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

The description implies using this tool to discover platform capabilities but does not provide explicit guidance on when to choose it over siblings or mention any prerequisites or exclusions. Usage context is implied but not explicit.

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