Zorqelio — Data Reliability for AI Agents

workspace_list

List contracts and aggregate usage belonging only to a private workspace. Requires its workspace API token.

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": {
      "workspaceToken": "<workspaceToken>"
    },
    "name": "workspace_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`operationId`	No
`workspaceToken`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It usefully discloses the authentication requirement ('Requires its workspace API token') and 'List' implies a read operation, but it does not describe pagination, rate limits, whether the operation is safe or read-only, or what the aggregate usage contains.

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 wording. The scoping detail is front-loaded, and the authentication requirement is stated plainly.

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

Completeness2/5

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

With no annotations, no output schema, and 0% schema description coverage, the description should do more to explain parameter behavior and return characteristics. It covers the purpose and token requirement but omits limit, operationId, and any indication of result structure or pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only clarifies one of the three parameters: workspaceToken as the workspace API token. It does not explain the meaning or constraints of the 'limit' or 'operationId' parameters, leaving significant gaps.

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?

The description uses a specific verb and resource: 'List contracts and aggregate usage.' It also states the scope: 'belonging only to a private workspace.' This is clear, but it does not explicitly distinguish itself from sibling contract tools such as contract_get or contract_compare.

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

Usage Guidelines3/5

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

The description implies usage by stating the tool lists contracts and usage for a private workspace, and it notes the required workspace API token. However, it gives no explicit when-to-use guidance, no exclusions, and no alternatives for listing broader or filtered contract data.

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

All Zorqelio — Data Reliability for AI Agents 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?