Skip to main content
Glama

list_guides

Retrieve a list of all running guides and educational articles. Browse training, pacing, and race preparation resources.

Instructions

List all running guides and educational articles on RunDida

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that executes the list_guides tool logic: fetches guides from the API, maps them to a formatted list, and returns the result as text content.
    async () => {
      const data = await fetchJSON(`${BASE_URL}/api/guides.json`);
      const list = data.guides.map(g => `- ${g.title} [${g.slug}] (${g.category}): ${g.description.slice(0, 100)}...`).join('\n');
      return {
        content: [{
          type: 'text',
          text: `RunDida has ${data.meta.total} running guides:\n\n${list}\n\nUse get_guide with a slug to see full details including FAQs.`,
        }],
      };
    }
  • index.js:356-371 (registration)
    Registration of the 'list_guides' tool on the MCP server using server.tool(), with a description and empty schema (no parameters).
    // Tool: list_guides
    server.tool(
      'list_guides',
      'List all running guides and educational articles on RunDida',
      {},
      async () => {
        const data = await fetchJSON(`${BASE_URL}/api/guides.json`);
        const list = data.guides.map(g => `- ${g.title} [${g.slug}] (${g.category}): ${g.description.slice(0, 100)}...`).join('\n');
        return {
          content: [{
            type: 'text',
            text: `RunDida has ${data.meta.total} running guides:\n\n${list}\n\nUse get_guide with a slug to see full details including FAQs.`,
          }],
        };
      }
    );
  • The fetchJSON helper function used by the handler to fetch data from the RunDida API with caching.
    async function fetchJSON(url) {
      const cached = cache.get(url);
      if (cached && Date.now() - cached.ts < CACHE_TTL) return cached.data;
    
      const res = await fetch(url);
      if (!res.ok) throw new Error(`HTTP ${res.status}: ${url}`);
      const data = await res.json();
      cache.set(url, { data, ts: Date.now() });
      return data;
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states the basic function without mentioning aspects like read-only nature, pagination, rate limits, or output structure. This is insufficient for a tool with no annotations.

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 a single sentence that is direct and free of filler, achieving maximum conciseness while conveying the essential purpose.

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 the tool has no parameters and no output schema, the description is fairly complete for a simple list operation. However, it could be improved by mentioning the read-only nature or the format of returned items, but it is not critically lacking.

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 has zero parameters, so schema description coverage is 100% by default. The description does not add parameter meaning, but that is acceptable since there are no parameters. Baseline for zero parameters 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 'all running guides and educational articles on RunDida', making the tool's purpose unambiguous. It distinguishes from sibling tools like get_guide, which focuses on a single guide.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as get_guide or calculate_pace. It lacks any mention of context, preconditions, or exclusions, leaving the agent without decision support.

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/XWeaponX7/rundida-mcp'

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