Skip to main content
Glama

occasioni.it: bandi e incentivi italiani

Ordina un servizio per l'utente

create_order

Orders a paid report. With an API key that has credit, it is paid at once and generated; otherwise it returns a checkout_url to hand to the human (Stripe), who pays and receives the report by email. Input depends on the product: verifica/bozza need ref (incentive id) and input (business profile + project); piano needs input (questionnaire answers); luogo needs ref (place id); kit needs input.cv, input.role and input.jobs (remote-job ids).

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": {
      "product": "<product>",
      "email": "<email>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoId della scheda (bando o comune) quando serve
emailYesEmail dell'utente che riceverà il report
inputNoDati per il report (profilo, progetto, risposte, CV)
productYesProdotto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product / enum
      Previous value: -[
      -  "verifica",
      -  "bozza",
      -  "piano",
      -  "luogo",
      -  "kit"
      -]New value: +[
      +  "verifica",
      +  "bozza",
      +  "dopo",
      +  "piano",
      +  "luogo",
      +  "kit"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that this is a monetary transaction, that the payment path depends on API key credit, that the fallback returns a checkout_url routed through Stripe to a human, and that delivery is by email. These are exactly the side-effect and cost details an agent needs before invoking a write tool.

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-loads the core behavior and payment branching in the first two sentences, then packs product-specific requirements into one dense final sentence. The compressed 'verifica/bozza need ref ... and input' phrasing is efficient but requires careful parsing; nothing is wasted, though it borders on telegraphic.

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 4-parameter tool with a nested input object and no output schema, the description covers the return path (checkout_url), delivery channel (email), and per-product input requirements well. It does not describe validation failures or what the response contains when payment succeeds immediately, leaving a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real conditional semantics the schema cannot express: it maps each enum value of product to which of ref/input (and which sub-keys of input: input.cv, input.role, input.jobs) are required. That resolves the ambiguity the schema leaves with its vague 'quando serve' wording.

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 verb+resource ('Orders a paid report') and immediately clarifies the transactional nature (paid, generated, or checkout flow). This clearly distinguishes it from read-side siblings such as get_order and list_products without needing their schemas.

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?

Gives explicit branching context: with a credited API key the order is paid and generated immediately; otherwise the caller must hand a checkout_url to a human. It does not explicitly name an alternative tool or state when not to call it (e.g. vs plan_preview or get_order), so usage routing is strongly implied rather than fully spelled out.

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