Skip to main content
Glama
blake365

Macrostrat MCP Server

by blake365

Timescale

timescale

Retrieve geological time period information by entering an age in millions of years before present. This tool provides detailed data about specific geological eras from the Macrostrat database.

Instructions

Get information about a time period

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageYesAge in millions of years before present

Implementation Reference

  • The handler function for the 'timescale' tool. It accepts an 'age' input, constructs a query to the Macrostrat API /v2/defs/intervals endpoint using timescale_id=11, fetches the data, and returns it as formatted JSON text.
    async (request) => {
      const { age } = request;
      const params = new URLSearchParams({
        timescale_id: "11",
        age: age.toString(),
      });
      const response = await fetch(`${getApiEndpoint("base")}/v2/defs/intervals?${params}`);
      const data = await response.json();
    
      return {
        content: [{
          type: "text" as const,
          text: JSON.stringify(data, null, 2)
        }]
      };
    }
  • Input schema specification for the 'timescale' tool, including title, description, and required 'age' parameter (number).
    {
      title: "Timescale",
      description: "Get information about a time period",
      inputSchema: {
        age: z.number().describe("Age in millions of years before present"),
      }
    },
  • src/index.ts:1054-1079 (registration)
    Registration of the 'timescale' MCP tool using server.registerTool, including the tool name, schema, and handler function.
    server.registerTool(
      "timescale",
      {
        title: "Timescale",
        description: "Get information about a time period",
        inputSchema: {
          age: z.number().describe("Age in millions of years before present"),
        }
      },
      async (request) => {
        const { age } = request;
        const params = new URLSearchParams({
          timescale_id: "11",
          age: age.toString(),
        });
        const response = await fetch(`${getApiEndpoint("base")}/v2/defs/intervals?${params}`);
        const data = await response.json();
    
        return {
          content: [{
            type: "text" as const,
            text: JSON.stringify(data, null, 2)
          }]
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get information' which implies a read-only operation, but doesn't specify what happens if the age is invalid, whether there are rate limits, authentication needs, or what format the information is returned in. For a tool with no annotations, this leaves significant behavioral gaps.

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, clear sentence with no wasted words. It's appropriately sized for a simple tool and front-loaded with the core purpose. Every word earns its place, making it efficient and easy to parse.

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

Completeness2/5

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

Given the tool has no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't specify what 'information' is returned (e.g., geological era, events, data format), leaving the agent unsure of the tool's full behavior. For a tool with no structured output documentation, the description should compensate more.

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?

The schema description coverage is 100%, with the parameter 'age' documented as 'Age in millions of years before present'. The description adds no additional meaning beyond this, as it doesn't explain how the age relates to the information retrieved or provide examples. With high schema coverage, the baseline is 3 even without param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get information about a time period' states a general purpose but is vague about what specific information is retrieved. It uses a verb ('Get') and resource ('time period'), but doesn't specify what type of information (geological, historical, astronomical, etc.) or how it relates to the 'age' parameter. It doesn't distinguish from sibling tools like 'mineral-info' or 'lat-lng-to-tile' which have different domains.

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 is provided on when to use this tool versus alternatives. The description doesn't mention any prerequisites, exclusions, or context for usage. With sibling tools like 'mineral-info' and 'find-units', there's no indication of when this tool is appropriate versus those for related queries about geological or measurement data.

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/blake365/macrostrat-mcp'

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