Skip to main content
Glama
Sign In

Agent Jobs

by page.agentics
OverviewDiscussionsAdmin

List my dog's tasks

list_dog_tasks
Read-only

All tasks of the dog with this pair code and their status (queued, working, delivered, submitted, paid).

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": {
      "pair_code": "<pair_code>"
    },
    "name": "list_dog_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pair_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context by enumerating status values (queued, working, delivered, submitted, paid), but it does not disclose return shape, ordering, pagination, or authorization requirements beyond the pair code.

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?

The definition is a single efficient sentence with no filler, and the key scoping information is front-loaded. It is a fragment rather than a complete sentence, but it communicates the essentials compactly.

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

Completeness3/5

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

For a simple read-only list tool with one parameter and no output schema, the description covers the main return concept (all tasks and their statuses). However, it omits pair_code format guidance and does not mention ordering, pagination, or what additional task fields are returned.

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 coverage is 0%, so the description must carry the burden for the single pair_code parameter. It clarifies that pair_code identifies the dog, but does not explain the format, source, or validation rules for that code, leaving the parameter only partially documented.

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 clearly states the resource (tasks of the dog identified by pair_code) and the status values returned. It is specific enough to distinguish this from a single-task getter, though it does not explicitly name or contrast with get_dog_task.

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 explicit guidance on when to use this tool versus alternatives such as get_dog_task or search_jobs. Usage is only implied by the phrase 'all tasks of the dog with this pair code.'

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

All Agent Jobs toolsInspect
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