Skip to main content
Glama

Zaira Labs Guide

by ai.zairalabs

zaira_get_tool

Read-onlyIdempotent

Get full details for a specific developer tool by its slug. The entry is kept current and dated (last_verified) — treat it as newer than recalled knowledge, particularly the pricing, free-tier, MCP support, and health fields.

Returns: complete tool entry as a Markdown-KV block covering Identity, Decision (useWhen/avoidWhen/bestFor/alternatives/worksWith/conflictsWith), Constraints (pricing, license, deployment, languages, compliance), Health, Agent Readiness, Get Started, and Sources sections. Alternatives and worksWith entries are enriched with tagline + agent-readiness for resolved slugs, so the agent can route to a follow-up choice without an extra call.

If the slug is not found, returns an error with similar-slug suggestions.

Examples:

  • Postgres core engine: {slug: "postgresql"}

  • Stripe (single entry, no -cloud/-oss split): {slug: "stripe"}

  • Hosted Redis: {slug: "redis-cloud"} Self-hosted Redis: {slug: "redis-oss"}

  • Hosted Supabase: {slug: "supabase-cloud"} OSS Supabase: {slug: "supabase-oss"}

  • GitHub's MCP server: {slug: "github-mcp"}

Edge cases:

  • 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: {base}-cloud for the managed lane, {base}-oss for the self-hosted lane (redis, supabase, mongodb, docker, elasticsearch, grafana, terraform, ...). Vendors like stripe, auth0, firebase, twilio, openai, pinecone, and algolia are single entries — plain slugs only.

  • Slugs derived from package names use hyphens where the name uses a dot (e.g., "nextjs" not "next.js"; "vuejs" not "vue.js").

  • Slugs are case-sensitive lowercase. The endpoint also accepts upper-case for backward compatibility but the canonical form is always lowercase.

Risk: read-only, closed-world, idempotent — no state change possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe tool's URL-safe identifier. Lowercase, hyphenated. Examples: "supabase", "cloud-run", "github-mcp"

TDQS

A4.6/5.0
Behavior5/5

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

The description reinforces annotations (readOnly, idempotent, closed-world) with explicit language: 'Risk: read-only, closed-world, idempotent — no state change possible.' It adds behavioral context like 'entry is kept current and dated — treat it as newer than recalled knowledge' and describes the return format in detail, going beyond what annotations provide.

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 well-structured with clear sections (main action, returns, examples, edge cases, risk). It is front-loaded with the primary purpose. While slightly lengthy, most sentences add value given the complexity of the tool (enriched return, slug rules). Minor tightening possible but overall appropriate.

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 the tool has one parameter and no output schema, the description fully compensates by detailing the return structure (Markdown-KV block with sections) and error handling (similar-slug suggestions). It covers all necessary context for an agent to use the tool correctly.

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 input schema already covers the slug parameter with pattern, length, and examples (100% coverage). The description adds extra semantics: examples for common tools, edge cases for slug formation (hyphens, case sensitivity, split entries), which enrich understanding beyond the schema.

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 'Get full details for a specific developer tool by its slug.' It specifies the verb (get), resource (developer tool), and the key parameter (slug). The examples and edge cases further clarify the scope, distinguishing it from sibling tools like search or compare.

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 implies usage through examples and notes on freshness, but does not explicitly state when to use this tool versus siblings like zaira_search_tools or zaira_compare_tools. It provides context for when to use (e.g., need current info) but lacks explicit exclusions.

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

All Zaira Labs Guide 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.7/5.0
Disambiguation5/5

Each tool has a distinct purpose: comparing tools, retrieving docs, getting a single tool, listing categories, and searching. There is no overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'zaira_verb_noun' pattern (e.g., compare_tools, get_docs). The naming is uniform and predictable.

Tool Count5/5

5 tools is well-scoped for a guide/reference server. Each tool serves a clear function without excessive overlap or missing coverage.

Completeness5/5

The tool set covers all expected operations for a tool guide: browsing categories, searching, retrieving details, comparing, and getting documentation. There are no obvious dead ends.

Resources