Agent Jobs

Get the next task from my dog

get_dog_task

Idempotent

WoofWoof.fun: fetch the next real job the owner queued for their dog, using the dog's pair code (e.g. ///neon.truffle.bark-1234). Use this whenever the user says "woofwoof go" (or "Los mit WoofWoof", "next", "weiter") with pair codes. Do the work, hand it back with deliver_work, then call this again until no tasks are left.

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

Input Schema

Name	Required	Description	Default
`pair_code`	Yes	The dog's pair code from the app.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the agent knows this touches state, presumably consuming or marking a task. The description adds the loop/termination behavior but never says what mutation occurs or what is returned when the queue is empty, which is the key ambiguity for a non-read-only call.

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?

Three sentences, front-loaded with purpose then triggers then follow-up workflow; little wasted wording aside from the marketing-style "WoofWoof.fun:" lead-in, which does at least anchor the domain.

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?

A one-parameter tool with no output schema, so the description should carry more about what comes back. It covers invocation and sequencing well but never describes the returned task shape or the empty-queue state, leaving the agent to discover the loop exit condition empirically.

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 100% and the single parameter is documented, so the baseline is 3; the description earns above that by supplying a concrete pair-code format example (///neon.truffle.bark-1234), which the schema's terse "from the app" does not provide.

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?

States a specific verb and resource: fetch the next queued job for a dog, keyed by the dog's pair code. The word "next" plus "real job the owner queued" implies single-item retrieval, which implicitly distinguishes it from a full listing like list_dog_tasks, but no sibling is named.

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 trigger phrases ("woofwoof go", "Los mit WoofWoof", "next", "weiter"), the prerequisite (pair code present), and a concrete workflow: do the work, hand it back with deliver_work, then call again until no tasks remain. That is when-to-use, what-next, and a termination condition all in one.

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

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