Skip to main content
Glama
ProsodyAI

@prosodyai/mcp-docs

Official
by ProsodyAI

List implementation recipes

list_recipes

List curated end-to-end implementation recipes for common ProsodyAI integration tasks, including adding prosody to LiveKit agents, streaming from browsers, wiring LangChain tools, and defining KPIs.

Instructions

List curated end-to-end implementation recipes for common ProsodyAI integration tasks (e.g. add prosody to a LiveKit agent, stream from a browser, wire the LangChain tool, define KPIs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the list_recipes tool. Calls listEntries('recipes') and formats the results.
    server.registerTool(
      "list_recipes",
      {
        title: "List implementation recipes",
        description:
          "List curated end-to-end implementation recipes for common ProsodyAI integration tasks (e.g. add prosody to a LiveKit agent, stream from a browser, wire the LangChain tool, define KPIs).",
        inputSchema: {},
      },
      async () => {
        const recipes = await listEntries("recipes");
        if (!recipes.length) return textResponse("No recipes bundled.");
        const lines = recipes.map((r) => `- ${r.id}  —  ${r.title}\n    ${r.description}`);
        return textResponse(lines.join("\n\n"));
      },
    );
  • Schema/definition for list_recipes tool with title, description, and empty inputSchema.
    {
      title: "List implementation recipes",
      description:
        "List curated end-to-end implementation recipes for common ProsodyAI integration tasks (e.g. add prosody to a LiveKit agent, stream from a browser, wire the LangChain tool, define KPIs).",
      inputSchema: {},
    },
  • src/server.ts:204-218 (registration)
    Registration of the list_recipes tool via server.registerTool.
    server.registerTool(
      "list_recipes",
      {
        title: "List implementation recipes",
        description:
          "List curated end-to-end implementation recipes for common ProsodyAI integration tasks (e.g. add prosody to a LiveKit agent, stream from a browser, wire the LangChain tool, define KPIs).",
        inputSchema: {},
      },
      async () => {
        const recipes = await listEntries("recipes");
        if (!recipes.length) return textResponse("No recipes bundled.");
        const lines = recipes.map((r) => `- ${r.id}  —  ${r.title}\n    ${r.description}`);
        return textResponse(lines.join("\n\n"));
      },
    );
  • Helper function listEntries that filters loaded content by section (used with 'recipes' section).
    export async function listEntries(section?: ContentSection): Promise<ContentEntry[]> {
      const all = await loadContent();
      return section ? all.filter((e) => e.section === section) : all;
    }
  • Helper function makeId used by loadContent to create stable IDs for content entries.
    function makeId(relPath: string): string {
      // strip extension; normalise slashes
      return relPath.replace(/\\/g, "/").replace(/\.(md|mdx|json|yaml|yml)$/i, "");
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as authorization needs, rate limits, or whether the list is cached. It only states it 'lists' recipes, offering minimal insight into side effects or constraints.

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?

Single sentence, front-loaded with verb and resource, includes relevant examples in parentheses. No wasted 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?

For a simple list tool with no parameters, the description adequately explains the content and provides examples. Could mention output structure but is sufficiently complete.

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?

There are no parameters, so the description adds value by explaining what the tool returns. With 100% schema coverage and no params, the baseline is 4.

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 verb 'List' and the resource 'recipes', specifying they are curated for common ProsodyAI integration tasks with concrete examples. This distinguishes it from siblings like list_docs and list_endpoints.

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

Usage Guidelines3/5

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

The description implies usage through examples of tasks, but does not explicitly state when to use this tool over alternatives or provide any exclusions.

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/ProsodyAI/mcp-docs'

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