Get User Info
get_user_infoRead-onlyIdempotent
Get information about the authenticated user
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
RationalBloks
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds the subject of the operation but does not disclose behavioral details such as auth requirements or response 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?
The description is a single, focused sentence with no redundancy or extraneous content. It is front-loaded and efficiently conveys the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with no parameters and good annotations, but without an output schema, the description's reference to 'information' is incomplete. It would be helpful to indicate common fields like username, email, or roles.
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?
The input schema has zero parameters, so there are no parameter semantics to explain. The description is not required to compensate for any missing schema information, and the baseline for zero-parameter tools is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Get' and identifies the resource as 'information about the authenticated user', which distinguishes it from sibling tools like get_project or get_graph_node. However, 'information' is somewhat vague about what exactly is returned.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives. It does not mention use cases like retrieving the current user's ID or profile, nor does it clarify exclusions or prerequisites.
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
A3.8/5.0
Disambiguation4/5
Most tools are clearly differentiated by domain (project vs graph_project) and action (create, get, list, delete). The main ambiguity is get_project vs get_project_info, which both claim to return detailed project information. Otherwise tool boundaries are clear.
Naming Consistency4/5
The server follows a strong verb_noun convention, with parallel naming for graph and non-graph tools (create_project/create_graph_project, deploy_staging/deploy_graph_staging). Minor deviations include bulk_create_graph_nodes and fulltext_search_graph, but patterns remain predictable.
Tool Count2/5
48 tools is a heavy surface, even when accounting for the two parallel product domains (relational and graph). Many tools are near-duplicates across domains, and the count exceeds the 25-tool threshold that feels manageable. It would benefit from consolidation or sub-servers.
Completeness4/5
Both project types have full life-cycle coverage: create, schema management, deployment, rollback, and deletion, plus graph data operations including bulk, search, and traversal. Minor gaps exist, such as no update_graph_relationship and the redundant get_project/get_project_info pair, but agents can accomplish core workflows.