Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Stack exposure dossier, live tier (premium)

get_cyber_dossier_live
Read-only

Stack exposure dossier, live tier (premium). Premium live tier: the stack exposure dossier re-pulled at call time. On the current snapshot build the live re-pull cannot complete, so the call serves the audited-snapshot dossier and names the degradation in the payload — no live freshness is claimed that was not performed. $5 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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": {
      "stack": "<stack>"
    },
    "name": "get_cyber_dossier_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackYesvendor or product name, e.g. PHP (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint/destructiveHint=false, the description discloses the critical behavior that the live re-pull cannot complete on the current build and the call serves the audited-snapshot dossier with the degradation named in the payload. It also spells out the 402 → PAYMENT-SIGNATURE → delivery handshake and that invoking the tool itself is free.

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?

The degradation caveat and the payment flow are front-loaded and each sentence carries information the agent needs. Slight redundancy between the title echo 'Premium live tier: the stack exposure dossier re-pulled at call time' and the opening line costs it the top score.

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 one-parameter, read-only tool with no output schema, the description covers the return value (x402 URL), the payment handshake, and the current degraded payload behavior. What the dossier itself contains is left unstated, but that is a minor gap rather than a blocker for correct invocation.

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 the single 'stack' parameter already carries an example ('PHP') and required flag, so the schema does the work. The description adds nothing about the parameter's accepted values or matching behavior, which is the expected baseline.

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 the resource (stack exposure dossier) and the differentiating tier (live/premium re-pull), plus what the call actually returns (an x402 URL). It never names a sibling such as get_cyber_exposure_dossier, so the contrast with the non-live variant is only implied through 'audited-snapshot dossier'.

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?

It gives real context for choosing this tool — premium tier, $5 USDC on Base, free to invoke with payment on the returned URL — and warns that live freshness is not actually delivered on the current build. It does not explicitly say when to prefer a cheaper/static alternative, leaving that inference to the agent.

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