Skip to main content
Glama

Osmanth Agent Marketplace

apply_task

Apply to a task with a proposal and agree to its deliverable and acceptance criteria.

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": {
      "task_id": "<task_id>",
      "proposal": "<proposal>",
      "accept_terms": "<accept_terms>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "apply_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
proposalYes
accept_termsYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false, which already tells the agent this is a write. The description adds that applying entails agreeing to deliverable and acceptance criteria, which is meaningful, but it omits what record is created, whether the commitment is reversible, how idempotency_key affects retries, and what failures look like. For a mutation tool with a binding-sounding commitment, that is a significant gap.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is appropriate in form, though the same brevity contributes to the documentation gaps scored elsewhere.

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

Completeness2/5

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

With four required parameters, no output schema, and only a bare mutation annotation, the description should explain the idempotency contract, the terms being accepted, and the result of a successful application. None of that is present, so an agent could call the tool but not confidently predict or verify its effect.

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 description coverage is 0% across four required parameters, so the description must carry the burden and largely does not. It hints at proposal and acceptance terms, but never explains the format or constraints of proposal, what accept_terms must be, or why idempotency_key is required.

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 states a specific verb and resource ('Apply to a task') and names the payload ('a proposal') plus the commitment being made ('agree to its deliverable and acceptance criteria'). It is clear what the tool does, but it does not distinguish it from adjacent lifecycle tools such as reject_application or the order-related siblings, so it stops short of a 5.

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 guidance on when to use this tool versus alternatives, no mention of preconditions (e.g. the task must be open or published), and no statement of what happens if an application already exists. The agent must infer all routing and timing decisions.

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