Skip to main content
Glama

search_augments

Find Teamfight Tactics augments by searching name or description. Use this tool to access accurate game data and prevent AI hallucinations about TFT mechanics.

Instructions

Search TFT augments by name or description. Omit the query to list all augments in the current set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search across augment name and description (uses FTS5)
limitNoMax results to return, 1-50 (default: 20)

Implementation Reference

  • The implementation of the `searchAugments` tool logic, which queries the SQLite database based on the provided search query.
    export function searchAugments(
      db: Database.Database,
      input: SearchAugmentsInputType,
    ): SearchAugmentsResult {
      const limit = input.limit ?? 20;
    
      let sql: string;
      const params: unknown[] = [];
    
      if (input.query) {
        params.push(input.query, limit);
        sql = `
          SELECT a.name, a.description
          FROM augments_fts fts
          JOIN augments a ON a.rowid = fts.rowid
          WHERE augments_fts MATCH ?
          ORDER BY fts.rank
          LIMIT ?
        `;
      } else {
        params.push(limit);
        sql = `
          SELECT name, description
          FROM augments
          ORDER BY name
          LIMIT ?
        `;
      }
    
      const rows = db.prepare(sql).all(...params) as Array<{
        name: string;
        description: string | null;
      }>;
    
      const augments: AugmentSummary[] = rows.map((row) => ({
        name: row.name,
        description: row.description ?? '',
      }));
    
      return { augments, total: augments.length };
    }
  • Input schema for the search_augments tool.
    export const SearchAugmentsInput = z.object({
      query: z
        .string()
        .optional()
        .describe('Free-text search across augment name and description (uses FTS5)'),
      limit: z
        .number()
        .min(1)
        .max(50)
        .optional()
        .default(20)
        .describe('Max results to return, 1-50 (default: 20)'),
    });
  • src/server.ts:167-177 (registration)
    Registration of the search_augments tool in the server.
    // 7. search_augments
    server.tool(
      'search_augments',
      'Search TFT augments by name or description. Omit the query to list all augments in the current set.',
      SearchAugmentsInput.shape,
      async (params) => {
        try {
          const result = searchAugments(db, params);
          return {
            content: [{ type: 'text' as const, text: formatSearchAugments(result) }],
          };
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the search functionality and the listing behavior when query is omitted, but lacks details on permissions, rate limits, error handling, or response format. It adds some context about the 'current set' but doesn't fully compensate for the missing 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?

The description is perfectly concise with two sentences that each earn their place: the first explains the core search functionality, the second provides important behavioral context about the query parameter. No wasted words, front-loaded with the main purpose.

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

Completeness3/5

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

Given 2 parameters with 100% schema coverage but no annotations and no output schema, the description provides adequate context for a search tool but leaves gaps. It explains what the tool does and when to use it, but doesn't describe the return format, error conditions, or authentication requirements that would be helpful for an agent.

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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description mentions the query parameter's purpose ('search by name or description') and the effect of omitting it, but doesn't add significant semantic value beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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's purpose with specific verbs ('search', 'list') and resources ('TFT augments'), and distinguishes it from siblings by specifying it searches 'by name or description' rather than other attributes. It explicitly mentions the scope ('current set') which differentiates it from other search tools.

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?

The description provides explicit guidance on when to use this tool versus alternatives: 'Omit the query to list all augments' indicates the behavior when no search is needed, and the context of searching 'by name or description' helps differentiate from sibling tools like search_champions or search_traits that presumably search different entities.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gregario/tft-oracle'

If you have feedback or need assistance with the MCP directory API, please join our Discord server