book_strategy_callGet the link to book a free Specularis strategy call about AI visibility / GEO / AEO.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| booking_url | Yes | Link to book a free 15-minute Specularis strategy call. |
Changes observed during successful MCP inspections.
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "booking_url": {
+ "description": "Link to book a free 15-minute Specularis strategy call.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "booking_url"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=true, so the agent already knows this is a safe, non-destructive read operation. The description confirms the action is simply retrieving a booking link, adding the detail that the call is free and topic-specific. No contradictions found. The description adds modest value beyond annotations but doesn't describe any return format details.
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 that describes the action, the cost (free), and the topic. Zero waste, every word earns its place. Ideal conciseness for a zero-parameter tool.
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?
For a zero-parameter tool with readOnlyHint=true and an output schema present, the description is essentially complete. It tells the user what they get (booking link), the subject matter, and that it's free. The only minor gap is not naming the sibling alternative explicitly, but the context signals show a clear distinction.
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?
With 0 parameters, the schema carries no semantic burden. The description explains what the tool returns (a link to book a free strategy call) and the topic, which is the entire semantic meaning needed. Since there are no params to document, and the description covers what the user gets, this is appropriate.
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 clear purpose: get the link to book a free strategy call about AI visibility/GEO/AEO. It specifies a concrete verb+resource ('Get the link to book') and describes the topic. It doesn't explicitly differentiate from siblings, but the sibling (run_ai_visibility_audit) is a distinctly different action, so this description is unambiguous about its purpose.
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?
The description gives context about what the call covers (AI visibility / GEO / AEO) and that it's free, implying when a user would want this. However, it does not explicitly state when to use this versus run_ai_visibility_audit, nor any exclusions or prerequisites. The when-to-use is implied by topic match rather than stated.
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.