Convocore

clients_read

Read-onlyIdempotent

Read Convocore client accounts (end-user workspaces under an agency/org). Actions: list, get, check_email. For action=list, default mode=compact (id/name/email/orgId). Use mode=full only when you need complete client objects; prefer action=get for one client. Not for organizations (use orgs_read) or CRM leads (use leads_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": "clients_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
`email`	No	For check_email.
`orgId`	No	Optional filter for list / check_email.
`action`	Yes
`clientId`	No
`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 beyond that by disclosing the cost tradeoff (compact is token-cheap, full is heavy) and the default mode applied when omitted. It does not cover pagination behavior, which keeps 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?

Three tight sentences, front-loaded with purpose, then actions, then mode guidance, then exclusions. Every clause carries actionable routing or cost information; nothing is redundant with the title or annotations.

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, three-action read tool with no output schema, the description covers the decision points that matter (which action, which mode, when to use a sibling). The remaining omission is pagination semantics and what check_email returns, which are minor for a read-only tool.

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?

With only 43% schema coverage, the description carries real weight: it explains the mode enum and its default, ties email to check_email, and implies clientId via 'prefer action=get for one client'. page, pageSize and clientId still lack any description, so a small gap remains.

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 a specific verb and resource ('Read Convocore client accounts') and immediately disambiguates the resource as 'end-user workspaces under an agency/org'. It enumerates the three supported actions and explicitly names the sibling tools it is not (orgs_read, leads_read), so an agent can distinguish it without opening the schema.

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: default to mode=compact for lists, escalate to mode=full only when complete objects are needed, and use action=get for a single client. It also names two exclusions with the correct alternatives (orgs_read for organizations, leads_read for CRM leads).

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?