Skip to main content
Glama
Snapstock MCP Server

Snapstock MCP Server

by sorndotdev

Get dataset metadata

get_dataset_info
Read-only

Retrieve bundled dataset metadata—coverage counts, data date, license, source, changelog URL, and citation guidance—to verify figures before citing them.

Instructions

Describe the bundled Snapstock snapshot: coverage counts, data date, license, source and changelog URL, and how to cite it. Use this before citing any figure.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes the useful framing that this is a bundled, static snapshot (consistent with openWorldHint=false) whose provenance and licensing it exposes. It does not say how large the response is or what the changelog URL points to, which would have pushed this higher.

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 clauses, zero waste: the resource and returned fields are front-loaded, and the usage directive lands as a short imperative. Nothing here is padding or restatement of the tool name.

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

Completeness5/5

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

With no output schema and no parameters, the description carries full responsibility for telling the agent what comes back, and it does so by naming each returned field. For a simple, zero-argument, read-only metadata lookup, nothing an agent needs in order to call it is missing.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline for a 0-param tool applies. Nothing in the description misrepresents the calling surface.

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?

States a specific verb ("Describe") and a specific resource ("the bundled Snapstock snapshot"), then enumerates exactly what is returned: coverage counts, data date, license, source, changelog URL, citation format. That enumeration makes it unmistakably distinct from the sibling ticker-scoring tools without needing to name one.

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

Usage Guidelines4/5

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

"Use this before citing any figure" is a concrete, actionable precondition that tells the agent when to reach for this tool rather than the analysis tools. It stops short of naming a specific alternative or stating when-not to use it, so it is a clear context cue rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.