Skip to main content
Glama

agent-ready-kit

by com.mudko

Get a self-selecting tier card

tier_selector
Read-onlyIdempotent

Use this when the user is in comparison_shopping mode or otherwise wants to pick a tier without sharing details. Returns 2-4 tier options with plain-language 'fits' descriptions so the user can self-identify. The user's tier choice is itself the qualifying signal — no buyer_context required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_requestYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tiersYes
statusYes
message_for_userNoPlain-language summary the calling agent can render to its end user. Never includes sales-pressure language.

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate safe, idempotent, read-only behavior. Description adds valuable context that user choice is the qualifying signal and no buyer_context needed, surpassing annotation coverage.

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?

Three sentences, front-loaded with usage guidance, no redundancy. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given existence of output schema, the description sufficiently covers purpose, usage, and behavioral context for a simple selection tool.

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 coverage is 0% and description does not explain the 'service_request' parameter or its nested 'natural_language_description' field. The description focuses on output and usage, not input semantics.

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?

Clearly states the tool returns 2-4 tier options for self-selection. Misses explicit differentiation from sibling 'get_pricing_tiers', but the context of avoiding detail sharing is distinctive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly specifies when to use (comparison_shopping mode, wants to pick a tier without details) and states no buyer_context required, guiding away from alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-ready-kit toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose, with descriptions that prevent confusion. Tools like scan_site and run_site_audit are differentiated by their focus on AI-readiness vs. site quality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, with clear action words like 'scan', 'create', 'get', 'verify'. Even longer names like 'summarize_scan_for_humans' maintain consistency.

Tool Count4/5

22 tools is slightly above the ideal range but justified by the comprehensive scope of the server, covering scanning, analysis, quoting, file delivery, and verification. Some tools like generate_files and get_customer_files could overlap but serve different contexts.

Completeness5/5

The tool surface covers the entire workflow from site scanning to deployment verification, with no obvious dead ends. All necessary operations for making a site agent-ready are present, including edge cases like x402 validation and credential verification.

Resources