get_profile
Return the authenticated customer's profile: name, account ID, balance, primary address, and payment method status.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Ezi Home Services
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It indicates a read operation returning specific data but does not disclose authentication requirements, rate limits, or potential side effects. Adequate for a simple read but lacks depth.
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, 20 words, clearly front-loaded with the purpose and a list of returned fields. No unnecessary information.
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?
With no output schema, the description lists the fields returned (name, account ID, balance, primary address, payment method status). However, it does not indicate data types or structure. For a simple profile tool, this is reasonably complete but could be enhanced with types.
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, so baseline is 4. The description adds no parameter semantics beyond the schema, which is comprehensive for zero parameters.
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?
Clearly states verb 'Return' and resource 'authenticated customer's profile' with a specific list of fields. Distinguishes from siblings that handle quotes, jobs, orders, etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Does not explicitly state when to use this tool versus alternatives or when not to use it. For a simple read-only profile retrieval, the context is implied but no exclusions or conditions are mentioned.
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: quoting, ordering, job cancellation, job rescheduling, profile retrieval, service availability lookup, scheduled jobs listing, and current datetime. There is no overlap or ambiguity.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern in snake_case, such as calculate_quote, cancel_job, get_profile, etc. No mixing of conventions.
Tool Count5/5
8 tools is well-scoped for a home services booking server. It covers the essential customer-facing operations without being too few or excessive.
Completeness4/5
The tool set covers the core workflow: checking services, getting quotes, creating orders, managing jobs (view, cancel, reschedule). Minor gap: no tool to update profile or payment method, but the surface is largely complete for the stated purpose.