Skip to main content
Glama
tristanlawrenceguy

Sameway

by tristanlawrenceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Find records

find_records
Read-onlyIdempotent

List records of any content type to get their IDs, filtered by title/word query, field conditions, and order. Use it to find notes, tasks, projects, events, or other items in Sameway.

Instructions

List records of a type to get their ids: all of them, those holding every word of the query in their title or words, or those matching where. The same where and order a collection block takes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesA content type, as the prompt lists it.
limitNoHow many to list. Defaults to 10.
orderNoA field, or -field for the largest or newest first. Newest first when left out.
queryNoWords each record found must hold, in its title or its words, in any order. Leave empty for every record.
whereNoConditions that must all hold. Each condition is field, operator, value with no spaces around the operator: status=draft, status!=done, title~garden (contains), due<today, due>=+7d, tags=health (has), body= (empty), due!= (set). Dates take 2026-10-01, today, tomorrow, yesterday, now, +7d, -1w, +3h. id!=abc123 leaves one record out, which is how a record lists the others like it. Order is a field name, or -field for the largest or newest first; created_at and updated_at work too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that the result is a list of ids rather than full records, which is a real behavioral trait beyond the structured metadata, though it omits ordering defaults and any limits/rate context.

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?

Purpose is front-loaded in the first clause and the second sentence is a compact cross-reference. The three-mode enumeration makes the opening sentence dense, but every clause carries information and nothing is padded.

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 no output schema, the description correctly fills the gap by stating the return is ids. Combined with a fully documented schema and read-only annotations, this is largely sufficient, though the pagination/limit behavior and the default ordering are left to the schema alone.

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 carries the semantics of all five parameters with rich examples. The description's 'the same where and order a collection block takes' is a cross-reference rather than added meaning, which is the baseline-3 case.

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?

States a specific verb and resource ('List records of a type') and immediately narrows the output purpose ('to get their ids'), covering three distinct retrieval modes. It does not, however, name or route against the closest siblings (get_record, search), so an agent must infer the boundaries itself.

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 three filtering modes (all / query / where) implicitly tell the agent which input to use, but there is no explicit when-to-use vs. get_record or search guidance, and no stated prerequisites or exclusions. Usage is implied rather than directed.

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