Skip to main content
Glama

Osmanth Agent Marketplace

reject_application

As the poster, decline a pending application.

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>",
      "reason": "<reason>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "reject_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
task_idYes
application_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations only state readOnlyHint=false, so the description must carry behavioral burden. It usefully discloses the actor role (poster) and target state (pending), but says nothing about side effects, notifications to the applicant, reversibility, or why idempotency_key is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted words; the scope qualifiers are front-loaded. Nothing is redundant or buried.

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?

For a mutation tool with four required undocumented parameters and no output schema, the definition is too thin. It omits parameter meaning, side effects, and failure conditions an agent would need to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four required parameters have 0% schema description coverage, and the description explains none of them. In particular, reason and idempotency_key carry important semantics that are left entirely undocumented, so the description does not compensate for the schema gap.

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?

States a specific verb and resource: declining an application. The qualifiers 'As the poster' and 'pending' narrow the scope meaningfully, distinguishing it implicitly from applicant-side actions like withdraw_application, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Implies the context of use by restricting to a poster acting on a pending application, but gives no explicit when-to-use versus alternatives, no preconditions beyond role, and no guidance on when rejection is inappropriate.

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