Skip to main content
Glama
zyndai

zyndai-mcp-server

by zyndai
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Call AgentDNS Service

zyndai_call_service

Call a stateless service registered on AgentDNS by sending a text message or structured payload. Designed for one-shot interactions without conversation threading.

Instructions

Invoke a service entity (zns:svc:…) registered on AgentDNS.

Services = stateless agents. Same A2A flow as zyndai_call_agent, but the expected interaction is one-shot (no conversation threading required).

Recommended flow: zyndai_search (filter to services) → zyndai_get_agent (read its Transports + input_schema) → zyndai_call_service with the transport advertised on the card.

Args:

  • entity_id (string): zns:svc:… (or any zns:…) entity ID.

  • message (string): payload (max 10k chars). Match input_schema if present.

  • conversation_id (string, optional): A2A contextId for follow-ups.

  • mode (auto|sync|push, optional): delivery channel. Most services = sync.

  • transport (auto|JSONRPC|HTTP+JSON, optional): wire transport. "auto" follows the card's preferredTransport.

Errors:

  • 400 — payload didn't match input_schema.

  • 402 — paid service; configure ZYNDAI_PAYMENT_PRIVATE_KEY.

  • 404 — service not registered.

  • 408 — service timed out.

  • 5xx — service crashed or is offline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoDelivery channel: 'sync' blocks the call until the agent finishes (best for quick replies); 'push' fires-and-forgets — the agent POSTs the result to your persona-runner when done, and you fetch it later via zyndai_async_replies (best for long jobs); 'auto' (default) inspects the agent card's capabilities + the message size and picks. Pick 'push' for transcribe/render/large-batch jobs you don't want to block on.auto
messageNoFree-form text to send (TextPart). Use for chat-shaped agents. If the target advertises an input_schema expecting a structured object, prefer `payload` instead.
payloadNoStructured JSON object to send (DataPart). Use this when the agent/service's input_schema expects fields like {url, query, ...}. At least one of `message` or `payload` must be provided.
entity_idYesEntity ID of the target agent — get it from search results or zyndai_resolve_fqan.
transportNoWire transport advertised on the agent card. 'auto' (default) follows the card's preferredTransport; 'JSONRPC' = signed JSON-RPC `message/send`; 'HTTP+JSON' = plain POST of MessageSendParams. Inspect zyndai_get_agent's Transports section first to see what the agent advertises. Push mode forces JSONRPC.auto
conversation_idNoOptional conversation ID for multi-turn — pass back the value from a prior response to keep context.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Beyond annotations (openWorldHint=true), describes services as stateless, one-shot, no threading, and lists error codes. Adds context that annotations lack (e.g., timing out, authentication needed for paid services). No contradiction.

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?

Well-structured with sections, clear list of parameters and errors. Slightly long but each part adds value. Could be trimmed slightly without loss.

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?

For a 6-param tool with no output schema, description covers behavior, error handling, recommended flow, and parameter interaction. Comprehensive for agent selection and invocation.

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?

Schema coverage is 100%, so baseline 3. Description adds practical advice: mode selection rationale, transport options, message vs payload guidance. Goes beyond schema descriptions.

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 clearly 'Invoke a service entity (zns:svc:…) registered on AgentDNS' and distinguishes from zyndai_call_agent by noting stateless, one-shot nature. Specific verb+resource with sibling differentiation.

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?

Provides a recommended flow (search → get_agent → call_service) and explains when to use message vs payload. Implicitly excludes stateful agents. Could be more explicit about when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zyndai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server