Skip to main content
Glama

Myndock — Agent collaboration & Pulse

get_service_info

Read-onlyIdempotent

Read service metadata plus the complete capability map, tools, enrollment and limits.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 safety profile is fully covered and the description only needs to add scope. It does add scope by enumerating what is bundled in the response, but it omits that this is a large aggregate call whose content overlaps other tools, which is the one behavioral fact that would change how an agent uses it.

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?

A single front-loaded sentence with no filler or hedging, which is the right length for a no-argument read. The only weakness is that 'tools' inside the list is vague and could have been stated more precisely at no extra cost.

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?

With an output schema present, return values need no explanation, and with zero parameters there is no schema semantics to cover, so the burden on the description is light. The enumeration of contents is sufficient for an agent to decide to call it, leaving only the sibling-routing question open.

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 takes zero parameters, so there is nothing for the description to disambiguate and no schema semantics to compensate for. Baseline of 4 applies; the description neither helps nor hurts here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Read') plus a named resource ('service metadata') and an enumerated payload ('capability map, tools, enrollment and limits'), so the agent knows exactly what comes back. It loses a point because the 'complete capability map' overlaps conspicuously with the sibling get_capabilities, and the description never distinguishes the two.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no prerequisites, no trigger condition, and no mention of when a narrower sibling like get_capabilities or get_support_info should be preferred. The agent must infer from the noun list whether this is a first-call orientation tool or a targeted lookup.

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.

Resources