Skip to main content
Glama

Starfile

What Starfile covers

starfile_overview
Read-onlyIdempotent

The datasets Starfile holds, how many records each has, how fresh each is, and links to the data feed and docs.

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": "starfile_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is free. The description adds real value by enumerating the payload contents (record counts, freshness, feed and doc links), which the agent could not otherwise know since there is no output schema. It does not describe whether freshness is a timestamp or a human-readable label, which keeps it below 5.

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?

A single sentence listing four returned elements with zero filler, and the resource is front-loaded. It is a noun phrase fragment rather than a declarative statement of what the tool does, which is the only structural weakness.

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?

With zero parameters, full annotation coverage, and no output schema, the description has to carry the return-value burden and largely does. Minor gaps remain: it does not say how many datasets to expect, how freshness is expressed, or that it is a natural entry point for the other tools.

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 tool takes no parameters and the schema is empty, so the baseline is 4. There is nothing parameter-level the description could clarify, and it correctly avoids inventing inputs.

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?

The description names the concrete inventory the tool returns: datasets held, per-dataset record counts, freshness, and links to feed and docs. That is specific enough for an agent to know it is a catalog/overview call rather than a search call. It stops short of naming a sibling it is preferred over, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent can infer this is a discovery step before querying a specific dataset, but the description never states 'call this first' nor excludes any alternative. No prerequisites or when-not-to-use conditions are given.

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