pricingReturn current HefestoAI prices (Free $0, PRO $8/month per user, OMEGA $19/month). Use it when the user asks what HefestoAI costs. Static text. Does not look up or change a subscription. No parameters: call it with {}.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| pro | Yes | PRO $8/month per user. | |
| free | Yes | Free tier, $0/month. | |
| omega | Yes | OMEGA $19/month. | |
| checkout | Yes | Checkout URL. |
Changes observed during successful MCP inspections.
Output schema / properties / omega / descriptionPrevious value: -"OMEGA: $19/month."New value: +"OMEGA $19/month."Output schema / properties / pro / descriptionPrevious value: -"PRO: $8/month."New value: +"PRO $8/month per user."Output schema / properties / founding_memberRemoved value: -{
- "description": "Founding-member price note.",
- "type": "string"
-}Output schema / properties / omega / descriptionPrevious value: -"OMEGA tier, $19/month."New value: +"OMEGA: $19/month."Output schema / properties / pro / descriptionPrevious value: -"PRO tier, $8/month."New value: +"PRO: $8/month."Output schema / properties / trialRemoved value: -{
- "description": "Trial terms.",
- "type": "string"
-}Output schema / requiredPrevious value: -[
- "free",
- "pro",
- "omega",
- "trial",
- "founding_member",
- "checkout"
-]New value: +[
+ "free",
+ "pro",
+ "omega",
+ "checkout"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "description": "Current HefestoAI prices. Static. The content text is this object as JSON.",
+ "properties": {
+ "checkout": {
+ "description": "Checkout URL.",
+ "type": "string"
+ },
+ "founding_member": {
+ "description": "Founding-member price note.",
+ "type": "string"
+ },
+ "free": {
+ "description": "Free tier, $0/month.",
+ "type": "string"
+ },
+ "omega": {
+ "description": "OMEGA tier, $19/month.",
+ "type": "string"
+ },
+ "pro": {
+ "description": "PRO tier, $8/month.",
+ "type": "string"
+ },
+ "trial": {
+ "description": "Trial terms.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "free",
+ "pro",
+ "omega",
+ "trial",
+ "founding_member",
+ "checkout"
+ ],
+ "type": "object"
+}Input schema / additionalPropertiesAdded value: +falseInput schema / propertiesRemoved value: -{}Input schema / requiredRemoved value: -[]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the payload is 'static text', it performs no lookup and no mutation, and it is parameterless so invocation is guaranteed side-effect free. It does not discuss rate limits or caching, but for a constant-return tool that is minor.
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?
Three short sentences, front-loaded with what is returned and the actual price data, followed by the usage trigger, the exclusion, and the calling convention. Every sentence earns its place with no filler.
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 shape need not be described, and annotations carry the safety profile. The description supplies the remaining essentials: trigger condition, negative scope, and empty-argument invocation, leaving nothing an agent needs in order to call it correctly.
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, which sets the baseline at 4. The description reinforces this with 'No parameters: call it with {}', removing any ambiguity about whether an argument is required, though it adds nothing beyond that confirmation.
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?
States a specific verb and resource ('Return current HefestoAI prices') and immediately names the concrete contents (Free $0, PRO $8, OMEGA $19). It also carves out what it is not ('Does not look up or change a subscription'), so an agent can separate it from siblings like analyze or compare 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit trigger ('Use it when the user asks what HefestoAI costs') and an explicit exclusion ('Does not look up or change a subscription'), which routes subscription-lookup intents elsewhere. Nothing is left to inference about when to call this tool.
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.