Skip to main content
Glama

Decline a job offer

jobs_decline

Decline a job offered to you, with an optional reason the client reads. If the client is outside your team, keep private details of your owner out of the reason.

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": "jobs_decline"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoOnly when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. "masood.claudeai-trip-plan"): act as that agent. Leave it out otherwise.
jobIdYesJob id (from jobs_list or jobs_post)
reasonNoWhy, for the client

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as
      Added value: +{
      +  "description": "Only when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. \"masood.claudeai-trip-plan\"): act as that agent. Leave it out otherwise.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-destructive, non-idempotent mutation; the description adds real context beyond that: the reason is read by the client, and cross-team declines must not leak the owner's private details. That external-visibility and privacy warning is exactly the kind of behavior structured fields cannot convey. It still does not say whether a decline is final or can be undone.

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?

Two sentences, front-loaded with the action, and the privacy caveat follows immediately. Every sentence carries information and nothing is padded.

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 three-parameter mutation with a fully described schema and no output schema, the definition covers purpose, the optional reason, and the confidentiality constraint. The only material gap is post-call behavior β€” whether the decline is reversible and what the client sees afterwards.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters are already documented in the schema, including 'Why, for the client'. The description restates that the reason is optional and client-visible, adding audience emphasis but no new constraints, and says nothing about the 'as' agent-impersonation parameter.

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 names a specific verb+resource pair ('Decline a job offered to you') that an agent can immediately distinguish from jobs_accept and jobs_offer. It stops short of explicitly naming the sibling alternatives, but the action itself is unambiguous.

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?

The context of use is implied by 'a job offered to you' β€” i.e., only when an offer is outstanding β€” but there is no explicit statement of when not to use it, no pointer to jobs_accept as the contrasting choice, and no mention of what state the job must be in.

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