Skip to main content
Glama

TAGLI - Branded Promotional Products

agentic_handshake

לחיצת יד ואימות ישות משפטית וייפוי כוח מוגבל תקציב מול מנוע המסחר (POST /tagli/v1/agent/handshake). Agent credentials and delegation proof must be passed strictly via HTTP transport headers (X-Tagli-Agent-Key, X-Tagli-Delegation-Token, Mcp-Session-Id), never in tool arguments.

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": {
      "principal": "<principal>",
      "mandate": "<mandate>"
    },
    "name": "agentic_handshake"
  }
}

Input Schema

NameRequiredDescriptionDefault
mandateYesNon-secret mandate parameters (such as max_authorized_budget_ils). Never place secrets here.
principalYesLegal entity details including legal_name, registration_id (ח.פ/ע.מ), and authorized_officer (name/full_name, email, phone).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that credentials and delegation proof travel in HTTP transport headers (X-Tagli-Agent-Key, X-Tagli-Delegation-Token, Mcp-Session-Id) and never in arguments, but says nothing about whether the call creates persistent state, whether it is idempotent, what happens on failed verification, or any rate limits.

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 dense sentences: the first states what and where, the second states the transport constraint. Front-loaded and free of padding, though mixing two languages in one definition slightly slows comprehension.

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

Completeness3/5

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

For a security-sensitive tool with nested objects and no output schema, the description omits what a successful handshake returns (session handle, delegation token, verification status) and any failure modes. The header-based auth constraint is the most valuable part and is present, but the picture is incomplete.

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% and nested fields (max_authorized_budget_ils, legal_name, registration_id, authorized_officer) are already documented in the schema, so the baseline of 3 applies. The one added signal is the instruction never to place secrets in the mandate object, which reinforces the schema note but adds no new meaning.

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 names the operation concretely — a handshake plus verification of a legal entity and a budget-limited delegation against the trading engine — and pins it to POST /tagli/v1/agent/handshake. That distinguishes it from the sibling quoting, estimation and order tools, though the Hebrew phrasing makes the verb+resource slightly harder to parse at a glance.

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 the notion of entity verification and delegation before trading, but there is no explicit statement of when this must be called versus agentic_quote or agentic_order_intent, nor any prerequisite/ordering guidance. The agent must infer that this is the entry step.

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