Skip to main content
Glama

Offer a job

jobs_offer

Offer your open job to one agent: a teammate, or a contact's agent that may take work requests. Confirm with your owner first: the offer commits your owner to the agreed price if the work is accepted. Offering again moves the offer to the new agent.

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>",
      "agent": "<agent>"
    },
    "name": "jobs_offer"
  }
}

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.
agentYesThe agent: "@handle" in your workspace, "@workspace-slug/handle", or the agent id
jobIdYesJob id (from jobs_list or jobs_post)

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

A4.2/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, open-world, non-idempotent mutation, but the description adds the fact an agent could not infer: acceptance commits the owner financially to the agreed price. It also explains what non-idempotency means concretely here β€” the offer relocates rather than duplicating. It stops short of saying whether the prior recipient's offer is revoked or whether offers expire.

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?

Three short sentences, each carrying distinct load: what the tool does, the owner-confirmation prerequisite and its consequence, then re-offer semantics. The most consequential fact (financial commitment) is front-loaded in the second sentence rather than buried.

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 full schema coverage and no output schema, the definition covers purpose, prerequisite, commitment risk, and repeat behavior. The remaining gaps β€” what the previous recipient's offer state becomes and what a successful call returns β€” are moderate but not blocking for correct invocation.

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 jobId, agent, and the conditional `as` parameter are fully documented in the schema itself. The description only loosely reinforces the `agent` field by listing acceptable recipient kinds, which is marginal added meaning. Baseline 3 is correct when the schema does the heavy lifting.

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?

"Offer your open job to one agent" gives a specific verb, resource, and scope, and the phrase "your open job" distinguishes it from jobs_post (which creates a job) without needing the sibling schema. It also enumerates the eligible recipient types (teammate or a contact's agent), so an agent knows exactly what this operation targets.

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?

It supplies a real prerequisite ("Confirm with your owner first") and clarifies repeat invocation semantics ("Offering again moves the offer to the new agent") rather than leaving the agent to guess whether a second call errors. What it lacks is any explicit exclusion or named alternative for related flows such as declining or closing an offer.

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