Semantic search across the active workspace's wiki (the 'brain'). Finds pages by MEANING — it matches even when you use different words than the page does. Returns ranked pages (title, slug, summary). Prefer this over pitchiq_v1_wiki_search_pages when you don't know the exact wording. Requires an active workspace.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | Natural-language query. Matches by meaning, not exact keywords. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses semantic matching behavior, return fields, and the active workspace requirement. It could add default limit behavior or pagination details, but the core traits are well covered.
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?
Four efficient sentences with no redundancy. Front-loaded with the core purpose, then behavior, then usage guidance. Every sentence adds value.
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?
Given no output schema, the description mentions return fields. It covers purpose, distinguishing behavior, prerequisites, and return format. Slight gap: no mention of pagination or ordering beyond relevance. Overall adequate for the tool's complexity.
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 coverage is 50% (query parameter described; limit parameter only has constraints). The description does not add parameter-level detail beyond the schema's existing query description. It adds workspace context but does not compensate for the undocumented limit parameter.
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 it performs semantic search across the active workspace's wiki, distinguishes it from the sibling tool pitchiq_v1_wiki_search_pages by noting it finds pages by meaning rather than exact wording, and specifies the return format (ranked pages with title, slug, summary).
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?
Explicit guidance: 'Prefer this over pitchiq_v1_wiki_search_pages when you don't know the exact wording.' Also states requirement for an active workspace, providing clear when-to-use and prerequisite context.
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.
Each tool has a distinct purpose covering booking, brain access, commerce quoting, and three separate discovery searches (creators, curators, podcasts). No two tools overlap in functionality, making selection unambiguous.
All tools follow the pattern 'pitchiq_v1_<category>_<action>', with consistent snake_case and clear categorization (booking, brain, commerce, discover). Actions are descriptive and uniform within categories.
Eight tools cover the server's apparent scope (booking, knowledge graph, discovery) without redundancy or omission. The count is well-scoped for the intended use cases.
While booking and discovery are reasonably complete, the brain component lacks write operations (create/update wiki pages), which limits agent ability to modify knowledge. The surface feels slightly incomplete for full workspace management.