Skip to main content
Glama

What Zodiacs can do

get_capabilities
Read-onlyIdempotent

Returns a list of what Zodiacs can do, its limits and how it handles privacy. It takes no input and needs no sign-in or birth details. It fits a question about what Zodiacs can do, or about its limits. It describes the service and calculates nothing. Zodiacs does not schedule anything, pick stocks or investments, make health predictions or guarantee outcomes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real value by stating it takes no input, needs no sign-in, requires no birth details, and performs no calculation. Those auth/privacy preconditions are not expressible in the schema. It stops short of describing shape or size of the returned list, which the output schema presumably covers.

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

Conciseness4/5

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

Front-loaded with the purpose, then scope, then exclusions, in four short sentences and no filler. The sentence about fitting a question about limits restates the opening clause slightly, and the negative list is a touch long, but each item plausibly earns its place as a scope boundary.

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 zero-parameter, read-only, output-schema-backed discovery tool this covers nearly everything an agent needs: purpose, no-argument behavior, no-auth precondition, and topic exclusions. The only residual gap is that it does not disambiguate against the explanatory sibling tool, leaving that routing decision implicit.

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?

With zero parameters the baseline is 4, and the description correctly confirms no input and no sign-in or birth details are needed, which prevents an agent from inventing arguments. No further semantic detail is possible for an empty object 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?

States a specific verb and resource ('Returns a list of what Zodiacs can do, its limits and how it handles privacy') and immediately contrasts with the rest of the catalog by saying it 'calculates nothing.' An agent can tell this is a self-describing metadata tool rather than a chart/calculation tool without opening the schema.

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?

Gives explicit when-to-use framing ('fits a question about what Zodiacs can do, or about its limits') and a strong set of exclusions (no scheduling, stocks, health predictions, guarantees). It never names a sibling tool as the alternative for those excluded topics, so routing on out-of-scope questions is left to inference, but the context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.