Cadourile.ro

create_gift

Adaugă un cadou nou într-o listă.

Args:
    list_id: ID-ul listei în care se adaugă cadoul.
    name: Numele cadoului (obligatoriu).
    description: Descriere opțională.
    price: Preț estimativ în RON.
    url: Link către produs. Nu se extrag metadate automat aici — folosește întâi
        extract_gift_metadata(url) ca să obții title/description/image_url/price,
        la fel ca formularul web.
    allows_contributions: Dacă lista poate contribui în comun la acest cadou (bifa
        „acceptă contribuții multiple" din web). Dacă nu e precizat, se activează
        automat când price >= 200 RON — identic cu comportamentul din formularul web.

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": {
      "list_id": "<list_id>",
      "name": "<name>"
    },
    "name": "create_gift"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No
`name`	Yes
`price`	No
`list_id`	Yes
`description`	No
`allows_contributions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already specify readOnlyHint=false and destructiveHint=false, so mutation behavior is clear. The description adds important context about default allows_contributions behavior tied to price threshold, which is not in annotations.

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?

Well-structured with a clear summary followed by parameter descriptions. Slightly verbose but each parameter note adds useful information. Front-loads the main purpose.

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?

Given no output schema and 6 parameters, the description covers purpose, parameters, and key behavioral defaults. It mentions the extract_gift_metadata workflow, though it could specify what happens on success (e.g., returns created gift). Overall, complete enough for an agent to invoke correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It explains each parameter's meaning, including the optional nature of description, the RON currency for price, and the conditional default for allows_contributions. This adds significant value beyond the bare schema.

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?

The description states a specific verb and resource: 'Adaugă un cadou nou într-o listă' (add a new gift to a list). It clearly distinguishes this creation tool from siblings like update_gift, get_gift, and create_gift_list.

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?

Mentions using extract_gift_metadata first for URL metadata, but does not explain when to use create_gift versus other gift-related tools or any prerequisites like list ownership. Usage context is implied but not fully specified.

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

All Cadourile.ro tools Inspect

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

Need Help?