List the available Tessera Analytics gold datasets with summaries and the plan (free/pro) each requires. Call first to discover what's available.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| datasets | Yes | ||
| your_tier | Yes | The caller's own plan (`free` or `pro`). Datasets whose `tier` is `pro` while this is `free` are visible for discovery but require an upgrade to read. | |
| generated_at | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behaviors. It correctly describes a read-only listing with summaries and plan, but lacks details on data freshness, access restrictions, or rate limits. Adequate for a simple listing tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with action and output description. No redundant words, every sentence serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple discovery tool with output schema. Describes purpose, output, and entry-point nature. Minor gap: no mention of authentication or data source.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters (0 params, 100% schema coverage). Description adds value by specifying output content (summaries, plan), which helps the agent understand what will be returned beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it lists available Tessera Analytics gold datasets with summaries and plan requirements. Verb 'List' and specific resource distinguish it from siblings like describe_dataset or get_download_url.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Call first to discover what's available', establishing it as the entry point. Does not specify when not to use or compare to alternatives, but the instruction implies priority.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a clearly distinct role in the data access workflow: discovering datasets, understanding schema, listing partitions, reading sample rows, and downloading full partitions. There is no meaningful overlap, and any potential overlap between read_dataset and get_download_url is explicitly disambiguated by row-cap versus full-bulk access.
All tool names follow a consistent verb_noun pattern using snake_case: describe_dataset, list_datasets, list_partitions, read_dataset, get_download_url. The pattern is predictable and makes the purpose of each tool immediately understandable.
Five tools is a well-scoped size for a market data access server. Each tool covers a necessary step in the user journey without redundancy or unnecessary surface area.
The tool set forms a complete workflow: discover available datasets, understand their schema, inspect available partitions, read bounded samples, and download full partitions for bulk access. There are no obvious gaps or dead ends for the stated market data purpose.