Skip to main content
Glama

agent-bank

by io.github.WirterNow

negotiate_job

Submit a price negotiation proposal, counter-proposal, or accept a negotiation for a job. Requires api_key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoAction: propose, counter-propose, or accept (defaults to propose)
job_idYesUUID of the job to negotiate
api_keyYesYour api_key from register_agent
messageNoOptional message with the proposal
counter_amountNoCounter-proposal amount (for counter-propose)
negotiation_idNoUUID of existing negotiation (for counter-propose/accept)
proposed_amountYesProposed payment amount
proposer_agent_idYesUUID of the proposing agent

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions the api_key requirement (already in schema) and does not state whether the operation is destructive, triggers notifications, or has side effects.

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?

The description is a single, front-loaded sentence with no extraneous words, efficiently conveying the core purpose.

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?

Despite 8 parameters and no output schema, the description is sparse. It omits the negotiation flow, success/error handling, and any prerequisites beyond api_key, leaving the agent with incomplete context.

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 description coverage is 100%, so baseline is 3. The description adds no parameter-level meaning beyond the schema; it does not explain relationships between action, counter_amount, and negotiation_id.

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?

The description clearly states the tool's purpose: submitting a price negotiation proposal, counter-proposal, or accepting a negotiation for a job. The verb 'submit' and resource 'price negotiation' are specific and distinguish it from sibling tools like 'create_job'.

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 description provides no guidance on when to use this tool versus alternatives like 'create_job' or 'accept_barter'. It only mentions a requirement (api_key) but does not specify context, prerequisites, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-bank toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools target distinct actions or resources, but there is potential overlap between 'browse_jobs_with_economics', 'find_matching_jobs', and 'list_open_jobs', which all relate to job discovery. Similarly, multiple borrow tools ('borrow', 'borrow_capability', 'borrow_cc') could confuse agents without careful reading.

Naming Consistency4/5

Tool names consistently use snake_case with verb_noun pattern. Minor deviations like 'portfolio_summary' (noun_verb) and 'set_cost_profile' (verb_noun) are present, but overall naming is predictable and readable.

Tool Count3/5

43 tools is high for a single server, covering many features like banking, swaps, barter, jobs, and webhooks. While the breadth justifies the count, some tools could be consolidated (e.g., multiple borrow tools) to reduce cognitive load.

Completeness4/5

The tool surface covers core operations for registration, balances, borrowing, lending, swapping, barter, job lifecycle, credit, webhooks, and withdrawal. Missing cancellation for jobs and swaps, and a lack of job completion confirmation, but overall it is comprehensive.

Resources