get_profile
Full registry profile (AgentReady Score, capabilities, sources).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
StackResolve
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden for behavioral disclosure. It indicates the profile contents but does not explicitly state that this is a safe read-only operation, whether any special authentication is needed, or how errors such as 'slug not found' behave.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact line that front-loads the core resource and adds a concise parenthetical of key contents. Every word earns its place, though it is arguably a noun phrase rather than a complete instruction.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, the description leaves important context missing: how to resolve the slug, what the response looks like, and how this profile differs from related registry tools. The listed components give a hint but are not sufficient for robust invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description never mentions the slug parameter, what it means, or how to obtain a valid value. With one required parameter and no compensation in the description, an agent cannot confidently construct a correct call.
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 identifies the resource as a 'full registry profile' and lists its main contents (AgentReady Score, capabilities, sources), so an agent knows what it returns. It is not a pure tautology because the parenthetical adds concrete detail. It does not strongly differentiate from siblings like get_company, but the resource is distinct enough.
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 given about when to use get_profile versus sibling tools such as get_company or list_registry. The description does not state prerequisites, exclusions, or a preferred context, leaving the decision entirely to the agent's inference.
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
C2.6/5.0
Disambiguation2/5
resolve and find_tools_for_task both return ranked tool recommendations for a task, and how_to also surfaces recommendedTools, making their boundaries unclear. search_tools adds further overlap as a registry search by query and requirements. The company/research and registry lookup tools are more distinct, but the task-to-tool cluster is genuinely confusing.
Naming Consistency4/5
The naming is almost entirely snake_case verb_noun: get_company, find_competitors, search_tools, compare_products, list_registry. The exceptions are audit and resolve as bare verbs and how_to as an idiom, but they are still recognizable.
Tool Count4/5
Fifteen tools is at the upper end of a reasonable range, and the broad scope of registry lookup, research, comparison, audit, and interface generation supports a larger surface. However, find_tools_for_task largely duplicates resolve, so the count is slightly higher than necessary.
Completeness4/5
The server covers the main registry lifecycle: listing, searching, getting records, comparing, researching, pricing, readiness auditing, and generating agent interfaces. It is intentionally read/research-oriented, so the lack of registry CRUD is not a severe gap. Minor missing pieces like direct per-product OpenAPI retrieval or registry entry management are workable around.