Skip to main content
Glama
astandrik

Codex Pets

by astandrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search Codex pets

search_pets
Read-onlyIdempotent

Find approved public Codex pet packs by query, kind, tags, author, or compatibility. Returns multiple candidates when exact slug is unknown.

Instructions

Use to discover one or more approved public Codex pet packs by query, kind, tags, author, or Codex compatibility. Prefer this over get_pet when you do not already have an exact slug or need multiple candidates. Do not use for private generation requests or known-slug install/share snippets; use get_pet_request_info or a slug-specific get_* tool instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional text matched against approved pet names, descriptions, tags, and authors.
kindNoOptional pet kind filter. Use all or omit the field to include every kind.
tagsNoOptional tag filter as a comma-separated string or array. All provided tags must match.
authorNoOptional author name text matched against the public submitter name.
compatibleWithNoOptional compatibility filter. Use codex for Codex-compatible pets; other values return no matches.
limitNoOptional maximum result count. Defaults to 10 and is clamped to 1-60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / author / description
      Added value: +"Optional author name text matched against the public submitter name."
    • addedInput schema / properties / compatibleWith / description
      Added value: +"Optional compatibility filter. Use codex for Codex-compatible pets; other values return no matches."
    • addedInput schema / properties / kind / description
      Added value: +"Optional pet kind filter. Use all or omit the field to include every kind."
    • addedInput schema / properties / limit / description
      Added value: +"Optional maximum result count. Defaults to 10 and is clamped to 1-60."
    • addedInput schema / properties / query / description
      Added value: +"Optional text matched against approved pet names, descriptions, tags, and authors."
    • addedInput schema / properties / tags / description
      Added value: +"Optional tag filter as a comma-separated string or array. All provided tags must match."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide readOnly, idempotent, non-destructive hints. The description adds that it searches only approved public Codex packs, which is beyond annotations. It does not mention pagination or response structure, but the schema's limit parameter addresses pagination.

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?

Two sentences, front-loaded with purpose, then usage guidelines. No unnecessary words.

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 no output schema, the description explains the tool's purpose and usage well. It could briefly mention what the returned packs contain, but the lack of output schema means this is not strictly required. The parameter count and enum are handled adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters have descriptions in the schema (100% coverage), so the description adds minimal param-specific information. It provides context for how parameters work together but does not clarify beyond 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 the tool discovers approved public Codex pet packs by various filters, using specific verbs and resource. It distinguishes itself from the sibling get_pet by noting it's for when an exact slug is unknown or multiple candidates are needed.

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 says when to prefer this tool (no exact slug, need multiple candidates) and when not to (private requests, known-slug snippets), naming alternatives like get_pet_request_info or slug-specific get_* tools.

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

Deploy Server

Other Tools