Skip to main content
Glama

Dryos

by ai.dryos
OverviewDiscussionsAdmin

List streams

list_streams
Read-onlyIdempotent

Every stream Dryos collects, with its entity column and headline measure.

Args:
    domain: Energy, Weather or Property.
    operator: A grid operator — ERCOT, MISO, PJM, SPP, CAISO, NYISO or ISO-NE.
    search: A word matched against the slug, name and tagline ("lmp", "wind", "permits").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNo
searchNo
operatorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds that each stream includes an entity column and headline measure, but says nothing about filtering, ordering, or pagination.

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?

The description is a single short sentence with no filler, front-loading the core content. However, the grammar is awkward and it omits a main verb, making it slightly less clear than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with optional filters, the description gives a minimal sense of output but omits parameter meaning and usage context. It has an output schema but the description does not leverage or summarize it sufficiently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

None of the three parameters (domain, search, operator) are described; the description does not explain how they filter or affect results. Since schema coverage is 0%, the description carries the full burden and fails to meet it.

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 title and description together indicate this returns all streams collected by the system, with each stream's entity column and headline measure. It is distinguishable from siblings like describe_stream or query_stream, but the description is a fragment and does not explicitly state 'list' or 'return'.

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?

No guidance is provided about when to use this tool over find_entities or query_stream, nor about combining the optional filters. The only hint is the title itself.

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

All Dryos 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