get_profileGet a detailed profile for a specific person by an id returned from search_people. Do not use this for names or natural language; call search_people first.
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | Profile id returned by search_people, not a person name |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context that the id must come from search_people, but it does not disclose other behavioral details such as return shape or error behavior. Given the annotations, a 3 is appropriate.
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?
Two sentences with no wasted words. The core function is front-loaded, and the critical usage caveat follows immediately. Every sentence earns its place.
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 simple single-parameter read-only lookup, the description is nearly complete: it states the resource, the source of the id, and the alternative. The lack of an output schema means it would be slightly better to hint at what 'detailed profile' includes, but this is not necessary for correct invocation.
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 description coverage is 100% and the userId parameter is already described as 'Profile id returned by search_people, not a person name'. The tool description reinforces this but does not add new parameter-level meaning beyond what the schema already provides, so the baseline of 3 applies.
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 specific verb and resource: 'Get a detailed profile for a specific person by an id'. It also explicitly differentiates from search_people by saying it is not for names or natural language, making its purpose unambiguous.
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?
It gives explicit when-to-use and when-not-to-use guidance: 'Do not use this for names or natural language; call search_people first.' This directly routes the agent to the correct sibling tool and clarifies the prerequisite.
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.
The auth/connection tools and people-search tools are clearly separated, and get_profile/search_people form an obvious workflow. The main overlap is me vs whoami, both exposing current-user information, though their descriptions point to different payloads.
Five tools follow a clear verb_noun snake_case pattern, but auth_status, me, and whoami break that pattern with noun, pronoun, and single-word names. The names are still readable, but the set lacks a consistent naming convention.
Eight tools is well within the well-scoped range for this server's auth and people-lookup purpose. Each tool has a clear responsibility in the workflow, and the count does not feel bloated or thin.
The tool set covers the full auth lifecycle with connect, disconnect, and status, plus a complete people lookup path from search to profile retrieval. There are no obvious dead ends for the server's apparent scope.