Skip to main content
Glama

handshake

Pre-delegation semantic handshake — full $0.25 / budget $0.10 (first full free once per operator+wallet, on proven wallet control)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "handshake"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefNo
shapeNo
party_aNo
party_bNo
rulingsNo
task_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does add genuine value on cost ($0.25 full, $0.10 budget, first full free per operator+wallet on proven wallet control), but says nothing about side effects, what a handshake yields, what "proven wallet control" verification entails, or whether the call mutates state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, so length is fine. However, the limited space is spent on pricing tiers rather than on purpose or parameters, so it is concise but misallocated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A six-parameter tool with nested objects, no annotations, no output schema, and no parameter documentation needs far more than a price tag. An agent has no basis to construct a valid call or predict the result.

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

Parameters1/5

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

Six parameters with 0% schema description coverage, including nested objects (party_a, party_b, rulings) whose internal shapes are undefined. The description explains none of them, leaving brief, shape, rulings, and task_id entirely opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Pre-delegation semantic handshake" restates the tool name (handshake) with an adjective and never states a concrete verb+resource or what the operation produces. It gives no differentiation from cite_contract or verify_contract, so an agent cannot infer the boundary between the three.

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?

"Pre-delegation" is the only temporal hint and is left implicit, with no statement of when this is required versus optional. There is no mention of the two sibling tools or of any precondition that would steer selection.

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