get_company_info
Get comprehensive information about Ruzora's services, process, value proposition, and differentiators.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
ruzora
by com.ruzora
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavior. It indicates the tool returns comprehensive information (not destructive), but doesn't mention any limitations like rate limits, auth requirements, or if results are cached. No contradiction with annotations since none exist.
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, well-structured sentence that front-loads the action ('Get comprehensive information') and specifies the scope. Every word adds value with no filler.
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?
Given the tool has no parameters and no output schema, the description sufficiently explains its purpose. It covers what information is retrieved, which is adequate for a simple info tool. Could mention that it returns static data or if it covers all updates, but for zero-param tools this is complete.
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 schema coverage is trivially 100%. The description adds value by clarifying what data the tool returns (services, process, value proposition, differentiators), which is not available elsewhere. No parameter explanations needed.
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 clearly states that this tool retrieves comprehensive information about Ruzora's services, process, value proposition, and differentiators. It uses specific nouns like 'services' and 'process' which distinguish it from sibling tools like 'list_open_roles' or 'get_job_details'.
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?
The name 'get_company_info' implies it's the right tool when an agent needs general company details, but there's no explicit guidance on when not to use it or how it compares to siblings. For instance, it doesn't say 'use this for high-level overview, not for specific job roles'.
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 addresses a distinct purpose: factory inquiries, hiring leads, company information, job details, open roles, demos, and candidate applications. There is no ambiguity in their target actions or stakeholders (client vs. candidate).
Naming Consistency4/5
Tool names consistently follow a verb_noun pattern using snake_case, such as create_factory_inquiry or list_open_roles. The minor inconsistency is that get_job_details and get_company_info use 'get' while others use 'create', 'list', or 'request', but the pattern is still predictable and clear.
Tool Count5/5
With 7 tools, the count is well-scoped for a recruitment and software services server. Each tool covers a necessary interaction (inquiries, applications, demos, info, role listing) without unnecessary bloat or deficiency.
Completeness4/5
The tool set covers the main lifecycle: company info, role discovery, applying/inquiring, and demo requests. A minor gap is the lack of update or delete operations for inquiries or applications, but for this domain those are typically handled out-of-band, so the surface is reasonably complete.