Convocore

orgs_read

Read-onlyIdempotent

Read organizations and related membership. Actions: list, search, get, list_clients, list_agents, list_members_and_teams, list_agent_org_clients. List/search actions default mode=compact (short fields). Use mode=full only when you need complete objects; prefer action=get for one org. Does NOT create/update/delete — use orgs_write. For end-user client accounts use clients_read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "orgs_read"
  }
}

Input Schema

Name	Required	Description
`mode`	No	compact (default): short summary fields only — token-cheap. full: complete API objects (heavy). Prefer get_* for one item.
`page`	No
`orgId`	No	Required for get / list_* (except list_agent_org_clients).
`action`	Yes
`search`	No	Search query for action=search.
`agentId`	No	Required for list_agent_org_clients.
`pageSize`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds value with token-cost guidance (compact default vs. heavy full mode), which annotations cannot express. It does not disclose pagination behavior or permission requirements, keeping it below a 5.

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?

Four short sentences, no filler, with the core purpose front-loaded and the mode/routing guidance following in priority order. Every sentence carries distinct information.

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?

For a 7-parameter, seven-action read tool with no output schema, the description covers the essential decision points (action selection, mode tradeoff, sibling routing). It stops short of describing what each action actually returns, which would be needed for full completeness without an output schema.

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 57%, so the description must compensate somewhat; it does this well for mode (default compact, cost implications, alternative get) and steers action=get for single-item reads. However, it only enumerates action values without explaining what each list_* action returns or requires, leaving some semantic gap.

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?

Opens with a specific verb+resource ('Read organizations and related membership') and then enumerates all seven supported actions, so an agent knows exactly the surface area it covers. It also explicitly disclaims the scope of orgs_write and clients_read, making it distinguishable from siblings without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use mode=full only when complete objects are needed, prefer action=get for a single org, use orgs_write for mutations, and use clients_read for end-user client accounts. Both when-to-use and when-not-to-use plus named alternatives are present.

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

All Convocore 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?