Skip to main content
Glama

Directory status

directory_status
Read-onlyIdempotent

Which chains lcas indexes, how far each is synced, and how many agents are hidden by content moderation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds that the output includes sync progress and a count of agents suppressed by content moderation, which is useful behavioral context beyond the annotations. It does not disclose freshness, cost, or whether the moderation count is global versus scoped.

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 compact sentence with no filler, and the most important concept (chains and their sync state) leads. The tradeoff is that the terseness leaves 'chains' and 'lcas' undefined, edging toward under-specification rather than waste.

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

Completeness3/5

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

With no output schema and no parameters, the description is the sole source of information about the return value, and it only enumerates three loosely phrased items. For a status/overview tool this is adequate to trigger a call but insufficient to tell an agent what fields or shape to expect.

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 no parameter meaning to convey and the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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

Purpose3/5

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

The description is a noun-phrase fragment that gestures at the payload (chain indexing status, sync progress, moderation-hidden agent counts) but never states a verb or a clear scope. 'Chains lcas indexes' uses an unexplained acronym, so an agent must guess what 'lcas' refers to. It is distinguishable from siblings like check_agent or find_tools only by vocabulary, not by an explicit statement of what this reports.

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, no prerequisites, and no mention of alternatives among the sibling tools (check_agent, check_endpoint, get_agent). The agent is left to infer that this is a diagnostic/overview call from the word 'status' alone.

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