Skip to main content
Glama
thyn-ai

Telys

Official
by thyn-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

telys_get

Read-onlyIdempotent

Retrieves exact rows from a collection by external IDs, returning found flags and stored metadata. For repo-indexed rows, re-reads source slices from disk to fetch code behind search hits.

Instructions

Exact row lookup by external id — no similarity search. Returns one entry per requested id with a found flag plus stored metadata; for auto-indexed repo rows the exact source slice is re-read from disk via the row's path + line range. Use to fetch known rows or read the code behind a telys_repo_search hit. Required: collection, ids. Optional: with_metadata (default true) and with_text (default true; re-read the source slice for repo-index rows). Unknown ids come back as found:false, not an error; fails only when the collection does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesexternal ids to look up exactly (no similarity search)
with_textNore-read the source slice for repo-index rows
collectionYesname of an existing collection in the active store
with_metadataNoinclude stored metadata for found rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / collection / description
      Added value: +"name of an existing collection in the active store"
    • addedInput schema / properties / ids / description
      Added value: +"external ids to look up exactly (no similarity search)"
    • addedInput schema / properties / with_metadata / description
      Added value: +"include stored metadata for found rows"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important behavior: unknown ids return found:false instead of error, failures only occur when the collection is missing, and repo-index rows trigger a disk re-read of the source slice. This adds meaningful context.

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 information-dense with no filler. The core exact-lookup purpose is front-loaded, and each subsequent clause adds distinct value: return shape, repo-row behavior, usage context, parameters, and error semantics.

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, the description compensates by specifying the return shape (one entry per id, found flag, metadata), the unknown-id behavior, and the only failure condition. It is complete for an agent to select and invoke correctly.

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 coverage is 100%, so the schema already documents all parameters and defaults. The description repeats required/optional status and the with_text re-read behavior, adding little beyond the schema. Baseline 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 states a specific verb and resource: 'Exact row lookup by external id' and explicitly contrasts with 'no similarity search.' It also names the related sibling telys_repo_search, making the tool's role clear.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool: 'Use to fetch known rows or read the code behind a telys_repo_search hit.' It also signals when not to use it by stating 'no similarity search,' which distinguishes it from search siblings.

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