Skip to main content
Glama

get_llms_txt

Retrieve the GeoTap API discovery document to access a structured overview of all available data sources and capabilities for environmental data from 80+ US federal sources.

Instructions

Get the GeoTap API discovery document. Returns a structured description of all data sources and capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler + registration for the 'get_llms_txt' meta-tool. Reads the llms.txt file from disk and returns its content, or returns an error message if the file is missing.
    // ── Tool: get_llms_txt (meta) ────────────────────────────────────────
    
    server.tool(
      'get_llms_txt',
      'Get the GeoTap API discovery document. Returns a structured description of all data sources and capabilities.',
      {},
      async () => {
        try {
          const content = readFileSync(join(__dirname, 'llms.txt'), 'utf-8');
          return { content: [{ type: 'text', text: content }] };
        } catch {
          return {
            content: [{ type: 'text', text: 'llms.txt not found. Visit https://geotapdata.com/llms.txt for documentation.' }],
            isError: true
          };
        }
      }
    );
  • src/index.js:274-291 (registration)
    Tool registration via server.tool() with name 'get_llms_txt', description, empty schema (no inputs), and async handler. The tool is registered on an McpServer instance imported from @modelcontextprotocol/sdk/server/mcp.js.
    // ── Tool: get_llms_txt (meta) ────────────────────────────────────────
    
    server.tool(
      'get_llms_txt',
      'Get the GeoTap API discovery document. Returns a structured description of all data sources and capabilities.',
      {},
      async () => {
        try {
          const content = readFileSync(join(__dirname, 'llms.txt'), 'utf-8');
          return { content: [{ type: 'text', text: content }] };
        } catch {
          return {
            content: [{ type: 'text', text: 'llms.txt not found. Visit https://geotapdata.com/llms.txt for documentation.' }],
            isError: true
          };
        }
      }
    );
  • Input schema for the tool — an empty object {} meaning the tool accepts no parameters.
    'Get the GeoTap API discovery document. Returns a structured description of all data sources and capabilities.',
    {},
  • The helper utilities used by the handler: readFileSync from 'fs' and path utilities (dirname, join) for resolving the llms.txt file path relative to __dirname.
    import { readFileSync } from 'fs';
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 behavior. It states the return value but omits side effects, authentication needs, rate limits, or other behavioral traits.

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 with no filler. Every sentence adds value: first states the verb and resource, second describes the return content.

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?

Without an output schema, the description should fully describe the return value. It says 'structured description' but lacks detail on format or structure, which is a gap for a tool that only outputs data.

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?

With zero parameters, schema coverage is 100% automatically. The description adds no parameter details, but baseline for 0 params is 4, which is appropriate.

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 it gets the GeoTap API discovery document, specifying the resource and action. It distinguishes from siblings 'collect_site_data' and 'get_results', which imply different operations.

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?

No guidance on when to use this tool versus alternatives. It does not mention that it should be used to discover capabilities before performing other actions.

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/jcholly/geotap-developer'

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