Skip to main content
Glama

agent_take

Idempotent

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Pick up one named ask on a YouGame game for your agent to build (the person you build for sent it to you, or you chose it from alpha_board), and get it as alpha_task gives it. Recorded as picked up by your agent: information, never a lock. Anyone may build any ask: someone else's claim is information for 24 hours, never a refusal. Refused when your agent already has as many asks here as it may at once, or when all four build slots hold open test builds (only an open test build uses a slot; a claim never does). Then build it on your own machine and call open_test_build with request = task.request.id, as for agent_wait.

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": {
      "game": "<game>",
      "request": "<request>"
    },
    "name": "agent_take"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesThe game's slug.
requestYesThe ask's id from alpha_board.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the OAuth/API-key auth requirement, that the pickup is a recorded signal rather than a lock, the 24-hour informational window on another agent's claim, and the exact refusal conditions (ask concurrency cap, four occupied build slots). It also clarifies that only an open test build consumes a slot while a claim never does — behavior that no annotation field conveys.

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?

Front-loads the auth blocker, then purpose, then semantics, then refusal rules and next step — a sensible order. Slightly dense with nested parentheticals and some overlap between "information, never a lock" and "someone else's claim is information for 24 hours, never a refusal," but each carries distinct detail.

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?

No output schema exists, and the return value is only indirectly specified via "get it as alpha_task gives it," which requires reading a sibling. However, auth, semantics, failure modes, and the required next call are all covered, which is substantial for a two-parameter pick-up 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?

Schema coverage is 100%, so the schema defines both parameters, but the description adds real meaning by tying 'request' to task.request.id in the subsequent open_test_build call and identifying 'game' as a YouGame game. That cross-tool mapping is not derivable from the schema text alone.

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?

Specific verb+resource: "Pick up one named ask on a YouGame game for your agent to build," with the return shape anchored to alpha_task and the source of the ask (the person you build for, or alpha_board). An agent can distinguish this from alpha_board (browsing) and alpha_task (reading) without opening any schema.

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

Usage Guidelines4/5

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

Explains the selection context (an ask sent to you or chosen from alpha_board) and states precise refusal conditions: per-agent concurrent ask limits and all four build slots holding open test builds. It also prescribes the follow-up (open_test_build with request = task.request.id). It stops short of an explicit "do not use this to browse; use alpha_board instead" exclusion, so it is clear but not fully comparative.

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