Skip to main content
Glama

work_catalog

General AI work: text, code, research, images, audio, video, computation or external actions. Open categories, encrypted files and buyer-selected acceptance; no default ranking.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses a few traits ('open categories', 'encrypted files', 'buyer-selected acceptance', 'no default ranking'), but never says whether this is a read-only listing, what the response looks like, or how categories relate to tasks and requests elsewhere in the toolset.

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?

It is a single compact sentence with the domain information front-loaded and no filler. It is efficient, though the terseness contributes to the ambiguity about what the tool returns.

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 and no output schema, the description is the only source of information about return values, and it doesn't describe them — an agent cannot tell whether it gets a list of categories, task templates, or prices. For a catalog tool in a large sibling set of explore/list tools, that leaves the caller under-informed.

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 and the schema is an empty object, so there is nothing for the description to compensate for. Baseline 4 applies.

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 enumerates the domain ('text, code, research, images, audio, video, computation or external actions') but never states a verb or says what the tool actually returns, so it reads as a content label rather than an action. An agent can guess this is the catalog of work types, but must infer that from the name rather than the text.

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 statement of when to call this versus siblings such as list_tasks, explore_tasks, or explore_task, which are the obvious near-neighbors. 'No default ranking' hints at how results are ordered but gives no trigger condition or exclusion.

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