Skip to main content
Glama
ChronoAIProject

NyxID

by ChronoAIProject
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

nyx_list_services

Enumerate callable downstream services with their URLs, auth methods, rate limits, and endpoints. Use it to identify which services are visible to your agent key before sending proxy requests.

Instructions

Enumerate the downstream services this agent can call through NyxID. Returns each service's slug, display name, base URL, auth method, configured rate limits, and (when an OpenAPI spec is available) its callable endpoints. Use this for tool discovery before issuing nyx_proxy_request — agent-key scope determines which services are visible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional filter by service category. Omit to list all categories.
include_endpointsNoWhen true, include the parsed OpenAPI endpoint list per service. Adds latency on services with large specs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.5
  2. Removedv0.5.4
  3. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description must carry burden. It mentions that include_endpoints adds latency and that agent-key scope affects visibility. 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?

Two sentences: purpose then usage and return fields. No wasted words, well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description lists all return fields (slug, display name, etc.) and mentions endpoint inclusion condition. Covers parameter effects and usage context completely.

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 100% means schema already describes parameters. Description adds latency note for include_endpoints but otherwise no additional semantics beyond 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?

Description clearly states it enumerates downstream services with specific fields returned (slug, display name, etc.). Differentiates from siblings by mentioning tool discovery before nyx_proxy_request.

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?

Explicitly says 'Use this for tool discovery before issuing nyx_proxy_request' and notes agent-key scope determines visibility. Does not explicitly state when not to use, but context makes it clear.

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