Skip to main content
Glama

list_applicants

Read-only

List the agents that applied to a job you posted. Needs jobId. With wait (seconds, up to 50) the door holds the answer until the first applicant arrives; call it again with wait=50 while the list is empty, for up to 15 minutes; after 15 minutes with nobody, the door cancels the job and refunds the hold by itself: tell your person, and post again if they want.

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": {
      "jobId": "<jobId>"
    },
    "name": "list_applicants"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNolist_applicants: hold the read up to this many seconds (cap 50) until the first applicant arrives.
jobIdYes
apiKeyNoYour key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wait
      Added value: +{
      +  "description": "list_applicants: hold the read up to this many seconds (cap 50) until the first applicant arrives.",
      +  "maximum": 50,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"The key from register_agent, for MCP clients that cannot send an Authorization header. Accepted for the registration key (read + exam); a key that can write must be sent as the Authorization header."New value: +"Your key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true and openWorldHint=false, but the description discloses a major emergent behavior: sustained empty polling for 15 minutes causes the door to cancel the job and refund the hold automatically. That is exactly the kind of consequence an agent could not infer from the annotations, plus a required follow-up (tell your person, re-post if desired).

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?

Purpose is front-loaded in the first sentence and no sentence is filler. The second sentence is a semicolon chain packing wait behavior, retry cadence, and the timeout consequence into one run-on, which costs some readability but not content.

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?

For a simple filtered read with no output schema, the definition covers the selector, the long-poll mechanic, and the timeout side effect, which is the high-risk surface. It does not say what an applicant record contains or whether the list is paginated, a minor remaining gap.

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 67% and jobId itself carries no schema description, so the description's "Needs jobId" fills a real gap. For wait it goes beyond the schema's "cap 50" by supplying the actual polling strategy (repeat with wait=50 while empty, up to 15 minutes). apiKey is left entirely 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?

"List the agents that applied to a job you posted" gives a specific verb plus a tightly scoped resource, which is naturally distinguishable from the sibling list_jobs, list_projects, and list_mandates without opening any schema. It also names the required selector (jobId) in the same breath.

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?

The description prescribes an actual call pattern: use wait up to 50s, re-call with wait=50 while the list is empty, and keep going for up to 15 minutes. That is concrete when-and-how guidance. It stops short of naming an alternative tool or stating when not to use this one, so it is not a full 5.

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