Skip to main content
Glama
Sign In

secondlife.it: lavoro, luoghi e soldi per ripartire

by it.secondlife
OverviewDiscussionsAdmin

Controllo rapido gratuito su un bando

quick_check
Read-only

Free first look at one call for a business: who may apply, size, region, sector, timing, and what the call asks on the bank and insurance side (loan, guarantee, fideiussione, mandatory catastrophe policy). Rule-based, no model. The full eligibility check (product "verifica") reads every requirement of the call.

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": {
      "ref": "<ref>"
    },
    "name": "quick_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesCodice del bando (il numero finale della pagina, o l'id incentivi:N)
sizeNoDimensione
regionNoRegione
sectorNoSettore
beneficiaryNoChi
already_startedNoLe spese sono già iniziate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds substantive context beyond that: the evaluation is 'rule-based, no model' (deterministic, not inferred), and it names the specific dimensions examined, including loan, guarantee, fideiussione and the mandatory catastrophe policy. No error or rate-limit behavior is mentioned.

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?

Three short sentences, front-loaded with the core promise and immediately followed by the routing hint to the full check. The parenthetical enumeration of bank/insurance instruments is slightly dense but earns its place by scoping the output.

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?

There is no output schema, so the description must convey what comes back, and it does: applicant eligibility, size, region, sector, timing and banking/insurance obligations. What is missing is any statement of the limits of the quick pass (e.g. that it does not verify every requirement), though this is partly implied by the contrast with 'verifica'.

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% with four enumerated fields, so the schema already explains every parameter. The description's listing of size, region and sector mirrors the input fields but adds no syntax, format or defaulting detail beyond the schema — the baseline 3 applies.

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 and resource ('free first look at one call for a business') and enumerates exactly what the result covers: who may apply, size, region, sector, timing, and bank/insurance requirements. It also distinguishes itself from the deeper 'verifica' check, so an agent knows this is the lightweight screening variant.

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?

Frames the tool as the free first look and explicitly names the alternative for exhaustive evaluation ('The full eligibility check (product "

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

All secondlife.it: lavoro, luoghi e soldi per ripartire toolsInspect
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