Skip to main content
Glama

Tineo

by ai.tineo.api
OverviewDiscussionsAdmin

Create Forwarding Address

forwarding_address_create
Idempotent

Create the authenticated user's personal Tineo forwarding address when they explicitly ask for one. Tineo reads email sent to that address and adds the travel bookings it finds to the user's trips, so the user can forward confirmations from any inbox or give it to a travel agent or booking site. Never replaces or changes an existing address: if one already exists it is returned unchanged. Use forwarding_address_get to read addresses without creating one.

Input Schema

NameRequiredDescriptionDefault
confirmedYesMust be true, set only after the user explicitly asks to create a forwarding address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / friendly_name
      Removed value: -{
-  "description": "Optional exact local-part after trips+ for a paid-Ultra personalized address.",
-  "maxLength": 40,
-  "minLength": 3,
-  "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
-  "type": "string"
-}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations by explaining what the address is for (email ingestion, booking extraction), its non-destructive/no-op behavior on existing addresses ('Never replaces or changes an existing address: if one already exists it is returned unchanged'), and hands off to the read sibling. This clarifies why idempotentHint is true in behavioral terms.

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 sentences, purpose front-loaded. Each sentence carries distinct value (what it is, what it enables, the no-replace guarantee, the alternative). Slightly longer than strictly needed but no wasted content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-param, no-output-schema tool, the description covers the required intent gate, the side-effect-free behavior on existing state, and the routing to the read sibling. Nothing needed to call it correctly is missing.

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 the single 'confirmed' parameter is already documented. The description reinforces the explicit-user-intent condition but adds no syntax or value detail beyond the schema, so 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 ('Create the authenticated user's personal Tineo forwarding address') and distinguishes itself from the sibling forwarding_address_get by naming it as the read-only alternative. An agent can tell what it does without opening the schema.

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 states the trigger condition ('when they explicitly ask for one') and names the alternative tool ('Use forwarding_address_get to read addresses without creating one'). Both when-to-use and how-to-avoid are covered.

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

All Tineo toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources