Skip to main content
Glama
Sign In

Algenta MCP Server

by io.github.thyn-ai
OverviewDiscussionsAdmin

get_source_schema

Read-onlyIdempotent

Advanced tool. Get the full schema for a specific registered source: column types, cardinality, fill rates, formula relationships, and detected join keys to other sources. Read-only and non-destructive; not separately rate-limited. Use list_sources to find source ids. Returns source_id and the full schema: column types, cardinality, fill rates, formula relationships, and detected join keys.

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": {
      "source_id": "<source_id>"
    },
    "name": "get_source_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYesSource ID from list_sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The description states 'Read-only and non-destructive; not separately rate-limited,' which matches annotations (readOnlyHint, destructiveHint=false) and adds the rate-limit detail beyond them. It also clarifies the return includes source_id and schema components. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively concise but repeats the list of schema components twice (once at the start, once at the end), adding redundancy. The 'Advanced tool' preface adds little value. Front-loading is decent, but trimming repetition would improve clarity.

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?

For a simple one-parameter read-only tool, the description covers the prerequisite (list_sources), the output components, and safety characteristics. No output schema exists, but the listed return fields give a good picture. It omits potential error handling or size limits, but that's minor for this scope.

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 description for source_id is already clear ('Source ID from list_sources'), and the description reinforces this by telling the agent to use list_sources. With 100% schema coverage, the added guidance on how to obtain the ID is helpful but not strictly necessary.

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?

The description clearly states the tool gets the full schema for a registered source, listing specific components (column types, cardinality, fill rates, formula relationships, join keys). It distinguishes the resource type (registered source) but does not explicitly contrast with sibling get_data_schema, which could cause confusion. Still, the purpose is concrete and actionable.

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?

It instructs to use list_sources to find source ids, which is a useful prerequisite. However, it does not mention when to avoid this tool or point to alternatives like get_data_schema, leaving some ambiguity for an agent deciding between schema tools.

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

All Algenta MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources