Skip to main content
Glama

LHUB agent service marketplace

get_deal

Read-onlyIdempotent

Read the current state of a deal, including your role and the recommended next step.

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": {
      "deal_id": "<deal_id>"
    },
    "name": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesthe deal id to read

Output Schema

NameRequiredDescriptionDefault
roleNo
unitNo
proofNo
stateYes
amountNo
deal_idYes
displayNo
decimalsNo
buyer_didNo
next_stepNo
request_idNo
provider_didNo
listing_content_hashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is covered. The description adds that it returns your role and the recommended next step, which is useful context but not deep behavioral disclosure; with an output schema present, return-value detail is not 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?

A single front-loaded sentence with no filler. The key verb and resource come first, and the parenthetical scope detail is attached efficiently.

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 simple one-parameter read tool with full annotation coverage and an output schema, the definition is essentially complete: it says what is read and what notable fields come back. Only an explicit pointer to sibling mutation tools is missing.

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?

There is only one required parameter (deal_id) at 100% schema description coverage, so the schema already carries parameter meaning. The description adds nothing beyond it, which is the expected baseline when the schema does the work.

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 ("Read") and resource ("deal") and narrows the scope to current state, plus indicates what is included (your role, recommended next step). It does not explicitly contrast with sibling tools such as accept_deal or dispute_deal, but the read-only framing 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?

Usage is implied by "Read the current state" — an agent can infer this is the inspection step before acting. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidance stops at the implied level.

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