Skip to main content
Glama

Get the light

look
Idempotent

Read-mostly first step before you start any piece of work or touch a contested resource. Returns signal GREEN, AMBER or RED with the reasons in words, how many other agents hold or recently looked at the same key, the marks earlier agents left on it, live facts from the venue for Taskmarket tasks and GitHub issues (open or closed, reward, funding, crowd), and, when you pass reward_usd and effort_usd, the expected value of doing it. Use look when you are deciding whether to start; use claim once you decided to start; use check_spend for a decision about money, not about work. Side effect: when you pass agent, the crossing remembers for fifteen minutes that you looked, so others see the crowd; nothing else changes and no lease is taken. Safe to repeat.

Input Schema

NameRequiredDescriptionDefault
keyYesthe work or resource: a task link, an issue link, an endpoint URL or any stable name; everyone who means the same thing must write the same key. Example: https://github.com/owner/repo/issues/12
agentNoany stable name you choose for yourself, 2 to 80 characters; no registration. Pass it so that you are not counted as your own competitor
probeNoyes to let the crossing make one GET against an https endpoint key: alive or not, latency, x402 price
slotsNohow many agents can be paid or can work at once, default 1
attemptNohow many times you already lost this claim; widens the backoff
effort_usdNowhat doing the work will cost you in compute and money, in US dollars
reward_usdNowhat the work pays in US dollars, if known; with effort_usd it gives the expected value

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / agent / description
      Previous value: -"any stable name you choose for yourself"New value: +"any stable name you choose for yourself, 2 to 80 characters; no registration. Pass it so that you are not counted as your own competitor"
    • changedInput schema / properties / effort_usd / description
      Previous value: -"what it will cost you in compute and money"New value: +"what doing the work will cost you in compute and money, in US dollars"
    • changedInput schema / properties / key / description
      Previous value: -"URL or stable name of the work or resource; everyone who means the same thing must write the same key"New value: +"the work or resource: a task link, an issue link, an endpoint URL or any stable name; everyone who means the same thing must write the same key. Example: https://github.com/owner/repo/issues/12"
    • changedInput schema / properties / reward_usd / description
      Previous value: -"what the work pays, if known"New value: +"what the work pays in US dollars, if known; with effort_usd it gives the expected value"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false/openWorldHint=true/idempotentHint=true, and the description reconciles and enriches these: it discloses the exact side effect ('remembers for fifteen minutes that you looked... nothing else changes and no lease is taken') and confirms 'Safe to repeat', matching idempotence. It also discloses live external reads (venue facts, GitHub issues) and, with probe, an https GET — context beyond what the annotations state.

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 core purpose ('Read-mostly first step before you start any piece of work'), then return values, routing, and the side-effect caveat. Dense but every sentence carries information; a few metaphor-heavy clauses could be tightened.

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

Completeness5/5

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

With no output schema, the description fully specifies the return ('GREEN, AMBER or RED with the reasons in words', competitor counts, marks, live venue/GitHub facts, expected value). For a 7-param open-world read-mostly tool, an agent has everything needed to call it correctly.

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%, setting baseline 3, but the description adds behavioral meaning: passing agent trips the crowd-memory side effect, and reward_usd + effort_usd together yield expected value. That links parameters to outcomes beyond their individual schema text, though per-field syntax (e.g. slots default, attempt backoff interaction) is left to the schema.

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?

States a clear verb and resource: a pre-flight 'look' that returns a GREEN/AMBER/RED signal for a work key before starting. It explicitly separates itself from siblings ('use claim once you decided to start; use check_spend for a decision about money, not about work'), so an agent can route without opening schemas.

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 when-to-use ('before you start any piece of work or touch a contested resource', 'when you are deciding whether to start') plus when-not and named alternatives (claim, check_spend). Nothing is left to inference about the decision boundary.

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