Skip to main content
Glama

Questions and answers

get_faq
Read-onlyIdempotent

Questions and answers about one template (photos, length, sound, price, pets, face swap or not) or, with no template, about Put Me In as a whole (price, refunds, privacy, account). Give a few words in question to get only the answers that mention them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_faq"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionNoa few words to look for, for example "refund" or "pets"
templateNoThe template, by its name or address name: tiny-desk, iphone-kupi-dance, gangnam-style-dance, bby-wow-dance, bad-times, bad-times-pet, stadium-entrance, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, bad-times-pet, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, tiny-desk, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: tiny-desk, iphone-kupi-dance, gangnam-style-dance, bby-wow-dance, bad-times, bad-times-pet, stadium-entrance, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  2. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: bad-times, bad-times-pet, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, tiny-desk, money-spread, toosie-slide, no-scrubs, you-tweaking-do-a-360, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  3. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, neon-dance, abcdefg-i-need-money, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  4. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The template, by its name or address name: bad-times, rumpelstiltskin, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"New value: +"The template, by its name or address name: bad-times, rumpelstiltskin, burning-bridges, hotel-lobby, my-ride-is-here, ghostface, bby-wow-dance, smalltown-boy, crazy-frog, zombie-couple, storm-dance, alors-on-danse, apt, topo-gigio, closed-on-sunday"
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior—keyword filtering ('only the answers that mention them') and template scoping—but says nothing about result volume, unmatched-keyword behavior, or what happens with an invalid template name.

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?

Purpose is front-loaded in the first clause and the fallback mode follows immediately. The dense parenthetical topic lists (photos, length, sound, price, pets, face swap) are wordy but do usefully signal coverage, so little is wasted.

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?

For a two-parameter, zero-required, read-only lookup with full schema coverage and rich annotations, the description covers both modes and the filtering semantics. The only gap is return-shape information, which matters slightly since no output schema exists.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: 'question' is a substring/keyword filter restricted to matching answers, and 'template' switches the whole answer corpus rather than just filtering it. That clarifies effect, not just type.

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?

States a concrete verb+resource: returns questions and answers, scoped either to a named template or to the product as a whole. That distinguishes it reasonably from sibling tools such as how_to_make and list_templates, though it never explicitly names those alternatives.

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?

Clearly explains the two usage modes: pass a template to get template-specific FAQ, omit it to get account/price/refund/privacy answers. It also tells the agent that a few words in 'question' narrows results, but it gives no explicit exclusions against how_to_make or get_example_prompts.

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.

Resources