Search the dataset
dataset_searchRows of the WallChartBook dataset whose cells contain the query (case-insensitive), up to 50.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | text to look for in any cell |
site
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It discloses case-insensitive matching and a 50-row cap, but it does not mention default limit behavior, ordering, empty-result handling, or whether full row objects are returned.
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?
A single, efficient sentence front-loads the key behavior and includes only valuable modifiers. It avoids restating the title or schema redundantly.
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?
For a simple two-parameter search tool, the description provides enough to invoke it correctly: dataset, query behavior, and result cap. However, with no output schema or annotations, it would benefit from stating the default limit and whether results are full row objects.
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 schema documents query's meaning but not limit. The description adds useful semantics by specifying cell containment, case-insensitivity, and the up-to-50 result cap. The default limit is left unspecified, but both parameters are otherwise understandable.
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 identifies the tool as returning rows from the WallChartBook dataset whose cells contain the query, with case-insensitive matching. This makes it easy to distinguish from sibling tools like dataset_columns, dataset_stats, or dataset_row.
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?
The matching semantics imply this tool is for full-text search across rows, but the description does not explicitly state when to use it over alternatives or mention any exclusions. Usage guidance is present only by inference.
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.
TDQS
A3.9/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but dataset_row and dataset_compare overlap for single-value equality checks, and dataset_search's substring match can also return exact matches. The descriptions largely resolve this, so the ambiguity is minor.
Naming Consistency4/5
All tool names use the same dataset_ prefix and lowercase snake_case, which is predictable and clean. However, the suffix mixes nouns (columns, row, stats, provenance) with verbs (compare, search) and the adjective-like 'top', so it is not a fully consistent verb_noun pattern.
Tool Count5/5
Seven tools is an appropriate size for a dataset-query server; each tool covers a distinct query pattern (schema, exact lookup, search, comparison, stats, ranking, provenance) without redundancy or bloat.
Completeness4/5
The server covers the core read-only workflows for the dataset: schema discovery, row retrieval, text search, comparisons, numeric summaries, top/bottom rankings, and citation metadata. It lacks a way to list all rows or get distinct column values, but these are workable gaps rather than dead ends.