Return current PH and US bucket pricing and the free-trial URL.
| Name | Required | Description | Default |
|---|---|---|---|
| team | No | Which team rates to return. Defaults to both. |
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | ||
| usBased | No | ||
| currency | Yes | ||
| freeTrial | Yes | ||
| pricingPage | Yes | ||
| allPlansInclude | Yes | ||
| philippinesBased | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "allPlansInclude": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "currency": {
+ "type": "string"
+ },
+ "freeTrial": {
+ "additionalProperties": false,
+ "properties": {
+ "creditCardRequired": {
+ "type": "boolean"
+ },
+ "hours": {
+ "type": "number"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "hours",
+ "creditCardRequired",
+ "url"
+ ],
+ "type": "object"
+ },
+ "model": {
+ "type": "string"
+ },
+ "philippinesBased": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "hours": {
+ "type": "number"
+ },
+ "monthlyRate": {
+ "type": "number"
+ },
+ "name": {
+ "type": "string"
+ },
+ "perHour": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "name",
+ "hours",
+ "monthlyRate",
+ "perHour"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "pricingPage": {
+ "type": "string"
+ },
+ "usBased": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "hours": {
+ "type": "number"
+ },
+ "monthlyRate": {
+ "type": "number"
+ },
+ "name": {
+ "type": "string"
+ },
+ "perHour": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "name",
+ "hours",
+ "monthlyRate",
+ "perHour"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "model",
+ "currency",
+ "allPlansInclude",
+ "freeTrial",
+ "pricingPage"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the data is 'current' (implying live, not cached) and that it includes a free-trial URL, which is modest but real added context.
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, front-loaded sentence with zero filler. The primary payload (BCN pricing) leads, and the secondary artifact (free-trial URL) trails.
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?
An output schema exists, so return-value explanation is unnecessary, and with zero required parameters and full schema coverage, an agent has everything needed to invoke the tool correctly. The description covers scope (PH and US) and content (pricing plus free-trial URL) adequately.
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?
Schema description coverage is 100%, so the single 'team' parameter and its ph/us/both enum are already fully documented in the schema. The description names PH and US, loosely echoing the enum, but adds no format or default semantics beyond what the schema provides.
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 states a specific verb and resource ('Return current PH and US bucket pricing') plus an additional artifact ('the free-trial URL'). The purpose is clear, but it does not differentiate itself from any sibling tool (list_services, match_intent, recommend_path, understand_site), which the 5-level requires.
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?
Usage is only implied: an agent infers this is the tool to call when pricing/free-trial information is needed. There is no explicit when-to-use, no when-not-to-use, and no mention of alternatives among the sibling tools.
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.