Skip to main content
Glama
Sign In
alpha-mcp

alpha-mcp

by rsc-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_rows

Fetch every row in a table where a column exactly matches a given value. Optionally limit results and select specific columns for read-only data lookup.

Instructions

Fetch every row where column = value (read-only).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>",
      "column": "<column>",
      "value": "<value>"
    },
    "name": "find_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows
tableYesTable name, as returned by list_tables
valueYesValue to match exactly
columnYesColumn to match, e.g. 'FundProvider'
columnsNoColumns to return; omit for all. Use it on FundsDataSets to skip the large JSON columns

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose 'read-only', which is a meaningful behavioral trait. However, it does not mention the limit parameter's default cap of 200 rows, which contradicts the implication of 'every row', nor does it address pagination, potential performance impacts, or result set size. The information is partially transparent but incomplete.

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, tightly worded sentence with no filler. It front-loads the core action and condition, and the read-only note is useful. Every word earns its place, making it exemplary in conciseness.

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?

An output schema is present, so return values are covered. However, the description lacks usage guidance and fails to clarify the limit behavior relative to the 'every row' claim. Given the tool's complexity (5 params, 3 required) and the existence of sibling tools, the description is adequate but not fully complete for correct invocation in all scenarios.

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?

Schema description coverage is 100%, so the schema already documents all parameters, including the limit, table, column, value, and columns fields. The description adds no additional parameter context beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states the verb ('Fetch'), the resource ('every row'), and the condition ('where column = value'), and explicitly marks it as read-only. This distinguishes it from sibling tools like get_row (single row) and list_tables (table listing), even without naming them.

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?

The description gives no guidance on when to use this tool versus alternatives such as get_row or list_tables. It only states the action and read-only nature, leaving the agent to infer the appropriate context. No exclusions or alternative conditions are provided.

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

Deploy Server

Other Tools