Skip to main content
Glama
Sign In
clavis-mcp-server

clavis-mcp-server

by KN0WBOT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_services

View all services configured in Clavis for the authenticated developer. Identify which API keys and integrations are active.

Instructions

List all services configured in Clavis for the authenticated developer.

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_services"
  }
}

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 the full burden. 'List' implies a read-only operation, and 'for the authenticated developer' gives context about authorization scope, but no details about side effects, permissions, rate limits, or return structure are disclosed. For a simple listing tool this is acceptable, but it is not rich in behavioral context.

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 a single sentence (12 words) that immediately states the action and scope. It is concise, front-loaded, and contains no filler or redundancy.

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?

For a tool with no parameters, no output schema, and no annotations, the description provides the essential purpose and scope. It omits explicit mention of return value details, but for a simple 'list all' operation the output is self-evident. Slightly more detail (e.g., pagination or result format) could make it more complete, but it is sufficient for the tool's simplicity.

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, and the schema coverage is 100% (vacuously). Per the rubric, a 0-parameter tool gets a baseline of 4. The description does not need to explain parameters, and there is nothing missing.

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 uses a specific verb ('List') and resource ('services configured in Clavis'), clearly distinguishing it from sibling tools like call_service, get_credentials, and check_credential_status. It also clarifies scope ('for the authenticated developer'), making the purpose explicit.

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 usage (when you need to enumerate services) but provides no explicit guidance on when to prefer this over alternative tools, nor does it mention any exclusions or caveats. Sibling names suggest different operations, but the description itself does not address them.

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