guide-registry

List organizational conditions

list_conditions

Read-only

List organizational conditions (identity, label, guide count, causal-role counts). Filter by draft domain, subdomain, or causal_role (driver|mediator|outcome). Names and counts only — no addresses, no passages.

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

Input Schema

Name	Required	Description
`q`	No	Substring match on the condition label.
`id`	No	Exact condition_identity_id. When set, other filters are ignored.
`limit`	No	Cap rows returned. Default 100, max 500.
`domain`	No	Draft domain slug, e.g. organizational-structure-and-culture.
`subdomain`	No	Draft sub-domain slug, e.g. organizational-learning-and-improvement.
`causal_role`	No	driver \| mediator \| outcome. Unknown values match nothing.

Output Schema

Name	Required	Description	Default
`count`	Yes
`filters`	Yes
`taxonomy`	Yes
`conditions`	Yes
`api_version`	Yes
`address_status`	Yes
`total_matching`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds useful behavioral context by specifying what the tool returns and excludes ('no addresses, no passages') and what filters are supported, going beyond the bare annotations.

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?

The description is two sentences with no wasted words. It front-loads the action and resource, then the returned fields, filters, and output limitation, making it easy for an agent to parse quickly.

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?

Given a detailed parameter schema, read-only annotations, and an output schema, the description covers the decision-relevant facts: what is returned, what filters are available, and what is excluded. Nothing an agent needs to call this tool correctly is missing.

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 description coverage is 100%, so the schema already documents all six parameters. The description summarizes the filter dimensions and output scope but does not add material information beyond the schema, so the baseline score of 3 is appropriate.

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?

The description uses a specific verb and resource ('List organizational conditions') and enumerates the returned fields (identity, label, guide count, causal-role counts). It clearly distinguishes this tool from siblings like list_guides and list_capabilities by naming the exact resource being listed.

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?

The description gives clear context for when to use this tool: when you need organizational condition metadata and counts. It also draws an explicit boundary with 'Names and counts only — no addresses, no passages,' signaling that this tool is not for full content retrieval, though it does not name a specific sibling alternative.

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

All guide-registry tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?