Blankas

blankas_issue

Start a verifiable agreement between two AI agents: issues a numbered, issuer-signed blank form for a deal, contract, order or service terms. Both parties then sign the same terms with their own keys, so each holds proof of agreement. Uses one free blank. Never send private keys.

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": {
      "party_a": "<party_a>",
      "party_b": "<party_b>"
    },
    "name": "blankas_issue"
  }
}

Input Schema

Name	Required	Description	Default
`party_a`	Yes	Public keys of party A: object with sign (Ed25519) and box (X25519), each 32 raw bytes as base64url without padding
`party_b`	Yes	Public keys of party B in the same format as party_a, different from party A

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful traits: it consumes one free blank (resource cost) and warns 'Never send private keys' (security constraint). It does not describe what is returned, whether issuance is idempotent, or how errors/duplicate issuance behave, which leaves notable gaps for a cryptographic write operation.

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 core action and immediately followed by the two-party signing rationale and key safety warning. Efficient and parseable, with only minor redundancy in the mid-sentence enumeration of agreement types.

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?

No output schema and no annotations exist, so the description should more fully cover what the issued blank form returns and how it chains to blankas_mark/blankas_verify. It explains the signing flow well but omits the return artifact and downstream tool relationship, leaving it only adequately complete.

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 the schema already documents party_a and party_b including key formats, making 3 the correct baseline. The description adds no parameter-level detail such as the constraint that the two parties must differ 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 states a specific verb+resource: 'issues a numbered, issuer-signed blank form' for deals/contracts/orders/service terms, and adds the two-party signing flow. It is clear what the tool does, but it does not explicitly distinguish itself from siblings like blankas_mark or blankas_verify.

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 'Start a verifiable agreement between two AI agents' and 'Uses one free blank,' giving the context in which it applies. However, there are no explicit when-not conditions or named alternatives among the sibling tools, so the agent must infer placement in the workflow.

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

All Blankas tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?