Returns the authenticated user's Departi profile: nationalities, current tax residence, subscription tier, a travel-history summary, and a live compliance snapshot (current Schengen / tax-residency / US-clock status). Requires authentication (OAuth). Use to personalise the other tools' answers, or to answer "where do I stand right now". Read-only; takes no parameters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses authentication requirements (OAuth), read-only nature, and the live compliance snapshot. These add behavioral context beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), informing the agent about side effects and prerequisites.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one well-structured sentence that fronts the core purpose, lists key data returned, mentions auth, gives usage guidance, and notes read-only/no parameters. No fluff, every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description enumerates the return contents sufficiently (profile fields plus live compliance status). The context signals (zero params, read-only, sibling context) are fully addressed; the tool is simple enough to be complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has no parameters (100% coverage by default), and the description explicitly states 'takes no parameters'. This is a zero-parameter case where the description adds no parameter detail but reinforces the absence, meeting the baseline of 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the authenticated user's Departi profile and enumerates specific content (nationalities, tax residence, subscription tier, travel history, compliance snapshot). This distinguishes it from sibling tools like check_tax and check_visa, which focus on specific queries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly provides use cases: to personalise other tools' answers and to answer 'where do I stand right now'. These instructions clearly imply when to use this tool versus the sibling check tools, offering practical context for an agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct need: compliance (visa, tax, Schengen), booking (accommodation, experiences, transport), and user profile. No overlap in purpose or outputs.
All tool names follow the consistent pattern departi_<verb>_<noun> (check_tax, check_visa, get_profile, search_accommodation, search_experiences, search_transport, track_schengen). Uniform snake_case and verb-first style.
Seven tools is well-balanced for the dual purpose of compliance and booking: three compliance tools, three booking tools, and one profile tool. Each earns its place.
Core compliance (visa, tax, Schengen) and curated booking (accommodation, experiences, transport) are covered. Minor gaps like ground transport or booking management are acknowledged and don't impede the primary workflow.
