Skip to main content
Glama
Storno CLI

Storno CLI

Official
by stornoro

spv_sync_prepare

Prepares an SPV inbox sync by returning the ANAF listaMesaje URL the local agent must GET with a qualified certificate, plus pending PDFs and optional report requests.

Instructions

Step 1 of an SPV inbox sync. Returns the ANAF listaMesaje URL the local storno-agent must GET with the qualified certificate (mTLS; the OAuth token is not accepted by SPVWS2), plus any PDFs still pending download. With includeRequests, also returns the periodic reports to place (the fisa rol once every 28 days): GET each anafUrl with the certificate and relay the answer with spv_request_agent_result; the balance is read when the answer is archived and an unpaid amount notifies the users. Relay the listing with spv_sync_agent_result.

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": "spv_sync_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to list (default and max: 60)
companyIdNoCompany UUID (overrides STORNO_COMPANY_ID env var)
includeRequestsNoAlso return the periodic ANAF reports due now (fisa rol every 28 days) as requests[] to place through the agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.59
    • addedInput schema / properties / includeRequests
      Added value: +{
      +  "description": "Also return the periodic ANAF reports due now (fisa rol every 28 days) as requests[] to place through the agent",
      +  "type": "boolean"
      +}
  2. Addedv1.0.28

TDQS

A4.3/5.0
Behavior4/5

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

Adds meaningful context beyond annotations: the required mTLS certificate, the fact that the OAuth token is rejected by SPVWS2, and that this tool returns URLs rather than fetching them. It does not explain what makes the operation non-read-only or non-idempotent, despite those annotation hints, leaving a small gap.

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?

Front-loaded with the key fact ('Step 1') and generally efficient, though the long semicolon-chained sentences make the procedural instructions denser than necessary.

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 multi-step orchestration tool with no output schema, the description does a good job of explaining return content and downstream relay steps. It could more explicitly describe any stored state created by the prepare phase, given the non-read-only annotation.

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%, so all three parameters are already documented. The description reinforces includeRequests by naming the periodic report cadence, but adds little for days and companyId beyond the schema's own descriptions.

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

Purpose5/5

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

States a specific role ('Step 1 of an SPV inbox sync') and exactly what it returns: the ANAF listaMesaje URL and pending PDFs. This clearly distinguishes it from spv_sync_agent_result (relay) and spv_request_agent_result (relay request answers).

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

Usage Guidelines5/5

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

Explicitly positions the tool as step 1 and tells the agent what to do with each output: relay the listing with spv_sync_agent_result, and, when includeRequests is set, GET each anafUrl and relay with spv_request_agent_result. The conditional path is stated rather than inferred.

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