get_connor_profile
Get Connor Gallic's profile: who he is, his role (AI Automation Architect, founder of MeetKai), what he builds, and his social links.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
connorgallic
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It describes the output content but omits behavioral details like read-only nature, authentication, or system effects. Adequate for a simple lookup tool.
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 clear sentence with no wasted words, front-loading the key action 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?
The description lists the categories of information returned (who, role, builds, social links) without an output schema, which is adequate for the tool's simplicity.
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 exist (0 params), so baseline 4 applies. The description adds no parameter info, but none is needed.
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?
The description explicitly states 'Get Connor Gallic's profile' with specific details (role, builds, social links), clearly distinguishing it from sibling tools like get_catalog or get_post.
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?
The description provides clear context (a specific person's profile) without explicitly stating when to use it over siblings, but the context is sufficient to infer usage.
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.