Skip to main content
Glama
Storno CLI

Storno CLI

Official
by stornoro

anaf_token_link_result

Read-onlyIdempotent

Poll a token link's status to see if it expired, was used, or completed, and retrieve the resulting tokenId, companyId, and exclusivity after authorization.

Instructions

Result of a token link you created: expired, used, completed, the tokenId the link produced (null until the holder has authorized), the companyId it was created for and whether it is exclusive. Poll this after sending a link to learn exactly which token came out of it, also when several links are authorized at the same time.

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": {
      "linkToken": "<linkToken>"
    },
    "name": "anaf_token_link_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkTokenYesThe linkToken returned by anaf_create_token_link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.59

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world characteristics. The description adds genuinely useful behavior: the tokenId is null until the holder authorizes, and the tool is intended for polling, which tells the agent how to interpret an empty tokenId rather than treating it as an error. It says nothing about polling cadence or failure modes for an invalid linkToken.

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, with the purpose stated first and the usage trigger second, so it is appropriately front-loaded. The first sentence is a dense run-on field list, but every field named carries information the agent cannot get elsewhere, since no output schema exists.

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 and a trivial one-parameter input, the description's job is to explain the shape of the result, which it largely does by enumerating the status flags, tokenId, companyId, and exclusivity. Only minor gaps remain: no guidance on what an expired or used status should prompt the agent to do next.

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 a single parameter with 100% schema description coverage, and the schema already explains that linkToken comes from anaf_create_token_link. The description only alludes to "a token link you created" without adding format or sourcing detail beyond the schema, so the baseline 3 applies.

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 specific resource (the result of a token link created via the sibling tool) and enumerates the returned fields (expired, used, completed, tokenId, companyId, exclusive). It is distinguishable from anaf_create_token_link by its result framing, though it does not explicitly name a sibling to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Poll this after sending a link" gives a clear trigger condition, and the phrase about several links being authorized at the same time clarifies a concurrent-authorization case. No explicit when-not-to-use or named alternative is given.

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

Deploy Server

Other Tools