get_ticket_purchase_policyUse this when a user asks how Dizko agents can buy tickets: signed quote, written confirmation, then a hand off to checkout unless a provider is integrated.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "anyOf": [
- {
- "properties": {
- "assistant_instruction": {
- "type": "string"
- },
- "autonomous_purchase_available": {
- "type": "boolean"
- },
- "current_default_behavior": {
- "type": "string"
- },
- "hard_rules": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "provider_contract": {
- "type": "string"
- },
- "supported_modes": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
- },
- "required": [
- "autonomous_purchase_available",
- "supported_modes",
- "hard_rules",
- "current_default_behavior"
- ],
- "type": "object"
- },
- {
- "properties": {
- "assistant_instruction": {
- "type": "string"
- },
- "cause": {
- "type": [
- "string",
- "null"
- ]
- },
- "classification": {
- "type": [
- "string",
- "null"
- ]
- },
- "code": {
- "type": [
- "string",
- "null"
- ]
- },
- "error": {
- "type": "string"
- },
- "hostname": {
- "type": [
- "string",
- "null"
- ]
- },
- "retryable": {
- "type": "boolean"
- },
- "status": {
- "type": [
- "number",
- "null"
- ]
- },
- "type": {
- "type": "string"
- },
- "url": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "error"
- ],
- "type": "object"
- }
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "anyOf": [
+ {
+ "properties": {
+ "assistant_instruction": {
+ "type": "string"
+ },
+ "autonomous_purchase_available": {
+ "type": "boolean"
+ },
+ "current_default_behavior": {
+ "type": "string"
+ },
+ "hard_rules": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "provider_contract": {
+ "type": "string"
+ },
+ "supported_modes": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "autonomous_purchase_available",
+ "supported_modes",
+ "hard_rules",
+ "current_default_behavior"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "assistant_instruction": {
+ "type": "string"
+ },
+ "cause": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "classification": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "code": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "error": {
+ "type": "string"
+ },
+ "hostname": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "retryable": {
+ "type": "boolean"
+ },
+ "status": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "type": {
+ "type": "string"
+ },
+ "url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+ ],
+ "type": "object"
+}Output schema / (root)Previous value: -{
- "anyOf": [
- {
- "properties": {
- "assistant_instruction": {
- "type": "string"
- },
- "autonomous_purchase_available": {
- "type": "boolean"
- },
- "current_default_behavior": {
- "type": "string"
- },
- "hard_rules": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "provider_contract": {
- "type": "string"
- },
- "supported_modes": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
- },
- "required": [
- "autonomous_purchase_available",
- "supported_modes",
- "hard_rules",
- "current_default_behavior"
- ],
- "type": "object"
- },
- {
- "properties": {
- "assistant_instruction": {
- "type": "string"
- },
- "cause": {
- "type": [
- "string",
- "null"
- ]
- },
- "classification": {
- "type": [
- "string",
- "null"
- ]
- },
- "code": {
- "type": [
- "string",
- "null"
- ]
- },
- "error": {
- "type": "string"
- },
- "hostname": {
- "type": [
- "string",
- "null"
- ]
- },
- "retryable": {
- "type": "boolean"
- },
- "status": {
- "type": [
- "number",
- "null"
- ]
- },
- "type": {
- "type": "string"
- },
- "url": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "error"
- ],
- "type": "object"
- }
- ],
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the bar is lower. The description earns credit by disclosing the actual content of the policy being retrieved — the quote/confirmation/checkout sequence and the provider-integration exception — which is behaviorally relevant context not present in any structured field.
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?
A single sentence, front-loaded with the usage condition and then the payload summary. No filler, no restatement of the title.
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?
With no parameters, no output schema, and annotations covering safety, the only open question is what the policy actually says — and the description answers that at a summary level. It doesn't state the response format (plain text vs. structured policy), a minor gap for such a simple read-only tool.
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 tool takes zero parameters, so the schema has nothing to explain and the baseline is 4. The description correctly avoids inventing parameter talk and instead spends its words on what the caller receives.
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 specifies the resource (the ticket purchase policy for Dizko agents) and summarizes what that policy covers: signed quote, written confirmation, checkout handoff, provider integration. It is clearly distinguishable from action siblings like quote_ticket_order and purchase_ticket_order, though the verb is implied by 'Use this when...' rather than stated outright.
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?
It gives an explicit trigger condition: 'Use this when a user asks how Dizko agents can buy tickets.' That routes the agent correctly away from the transactional siblings, but no when-not condition or direct sibling reference is provided for the cases where the user actually wants to buy rather than understand the process.
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.