list_services
The services Virohana offers. Call service_detail() for the full write-up.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
site
TDQS
A3.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description lacks any disclosure about side effects, read-only nature, rate limits, or ordering. For a list operation, it is likely safe, but the description does not confirm this.
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 extremely concise at two sentences, front-loading the purpose and including a useful sibling reference without any extraneous information.
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?
Given zero parameters and an output schema, the description covers basic purpose and sibling differentiation. However, it does not differentiate from other listing siblings (list_journal, list_products), limiting completeness for an agent context.
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 tool has zero parameters, so the description is not required to add parameter meaning. Baseline for 0 parameters is 4, and no additional parameter information 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 clearly states the tool lists services offered by Virohana, using a specific verb 'list' and resource 'services'. It also hints at the distinction from sibling `service_detail` by suggesting use of that tool for full write-ups.
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 explicit guidance on when to use `service_detail` instead, but does not specify contexts where `list_services` is preferable over other listing siblings like `list_journal` or `list_products`.
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
Disambiguation5/5
Each tool has a distinct purpose: about_virohana provides background, list_journal and read_post handle journal content, list_products and product_detail handle products, list_services and service_detail handle services, search_site provides cross-domain search, and start_here offers a guided tour. No two tools overlap significantly.
Naming Consistency4/5
Tool names use snake_case consistently, with a pattern of 'verb_noun' for lists (list_journal, list_products, list_services) and 'noun_detail' for details (product_detail, service_detail). However, about_virohana and start_here break the pattern slightly, and read_post and search_site are descriptive but not exactly verb-noun. Overall, naming is clear and predictable.
Tool Count5/5
With 9 tools, the set is well-scoped for a company information site. It covers core functions: about, journal, products, services, search, and a guided start. No tool is redundant, and the count is appropriate for the domain.
Completeness5/5
The tool surface provides comprehensive coverage of the Virohana site: background (about_virohana), journal listing and reading (list_journal, read_post), product listing and details (list_products, product_detail), service listing and details (list_services, service_detail), full-site search (search_site), and an entry point (start_here). There are no obvious gaps for a read-only informational website.