get_catalog
Get the full machine-readable catalog: profile, products, ventures, open source, writing, actions, and endpoints.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
connorgallic
TDQS
A4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states what the catalog contains, not any behavioral traits like read-only, auth needs, or return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no wasted words; front-loaded with verb and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a parameterless tool with no output schema; lists all major components. Could mention return format but 'machine-readable' hints at JSON.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters in input schema, so description adds value by listing catalog components, meeting the baseline for 0-param tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'Get' and resource 'full machine-readable catalog', listing components that clearly distinguish it from sibling tools like get_connor_profile or list_products.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for retrieving the entire catalog, with siblings covering specific items. No explicit when-not or alternatives, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: catalog overview, personal profile, single blog post, products list, reading log, writing list, and action recommendation. No apparent overlap or ambiguity.
Naming Consistency5/5
All tool names follow a consistent 'verb_noun' pattern with 'get', 'list', and 'recommend' verbs, making it predictable and easy to understand.
Tool Count5/5
Seven tools is ideal for this personal portfolio server, covering profile, products, blog, reading log, and a recommendation action without being too sparse or overwhelming.
Completeness4/5
The tool surface covers the main aspects of the personal brand: profile, products, writing, reading log, and a recommendation. A minor gap is the lack of a tool to list all categories or tags, but filters partially address this.