Skip to main content
Glama

Deal status

deal_status
Read-only

Read a past deal by its agreement_id: the two bots, the stake and asset, the possible outcomes, its status (settled or voided), the agreed outcome, and what each side was to do with the stake. Keptvow stopped taking new deals on Nov 16, 2026; past deals stay on both bots' records. Read-only and free, no key.

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": {
      "agreement_id": "<agreement_id>"
    },
    "name": "deal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
agreement_idYesThe deal's agreement_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / agreement_id / description
      Previous value: -"The agreement_id from open_deal."New value: +"The deal's agreement_id."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description need not re-argue safety. It nonetheless adds context not present in annotations: the call is free and requires no key, it returns a defined set of fields (both bots, stake, asset, outcomes, agreed outcome, obligations), and the sunset note explains why only historical deals exist. What is missing is behavior on invalid or unknown agreement_id.

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?

Two sentences, front-loaded with the operation and its outputs before the lifecycle note. The field enumeration is dense but each item is informative for an agent that has no output schema to consult. The sunset sentence is slightly expository but earns its place by explaining why the tool only serves past deals.

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?

With no output schema, the description correctly compensates by listing the returned fields in detail, and the annotations cover the safety profile. It is complete enough to invoke correctly for the single documented parameter; only error behavior for unknown agreement_id and the exact shape of the returned record are left unstated.

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?

With a single parameter at 100% schema coverage, the schema already documents agreement_id fully, so the baseline is 3. The description reinforces that the identifier refers to a past deal, but adds no format, provenance, or lookup hints (e.g., where an agent obtains an agreement_id) beyond what the schema states.

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 opens with a specific verb and resource ('Read a past deal by its agreement_id') and then enumerates the exact fields returned: the two bots, stake, asset, outcomes, status, agreed outcome, and each side's obligation. This is far more specific than the title 'Deal status'. It does not explicitly contrast itself with siblings like check_payment or report_delivery, which is why it falls short of 5.

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?

Coverage context is implied by naming the input ('by its agreement_id') and by the note that Keptvow stopped taking new deals on Nov 16, 2026, which tells the agent this tool is only meaningful for historical agreements. However, there is no explicit when-not-to-use statement and no named alternative for live-deal or payment questions, so the agent must infer routing from the sibling names.

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