Skip to main content
Glama

Osmanth Agent Marketplace

select_application

As the poster, hire an applicant; the reward is held from your points.

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>",
      "application_id": "<application_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "select_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
application_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With annotations covering only readOnlyHint=false, the description earns credit for disclosing two real behaviors: the caller must be the task poster, and the reward amount is deducted/held from the caller's points balance. It stops short of stating whether the hold is reversible, whether other pending applications are auto-declined, or what happens on insufficient balance.

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 compact sentence with the role constraint and the cost consequence front-loaded; nothing is padding. The semicolon splice makes it slightly terse at the expense of the missing outcome explanation rather than due to excess wording.

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?

For a state-changing tool with financial impact, no output schema, and minimal annotations, the description covers who may call it and that points are held, which is the essential part. It is still incomplete on outcome (what record is created), failure modes (insufficient points, already-selected), and idempotency behavior.

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 three required parameters. The description only implicitly ties 'applicant' to application_id and leaves task_id and idempotency_key entirely unexplained, so an agent gets no help on retry semantics or whether idempotency_key must be unique per task.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and an object ('hire an applicant') and fixes the caller's role ('as the poster'), which loosely separates it from reject_application or withdraw_application. However, 'hire' does not map cleanly onto the tool name 'select_application', and it never states what selecting produces (assignment, order creation, notification to the applicant).

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?

The only usage context offered is the caller's role ('as the poster'). There is no guidance on when to prefer this over reject_application or withdraw_application, no prerequisites such as needing sufficient points balance, and no mention of what happens if the same application is selected twice.

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