Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

list_profiles

Read-only

Retrieve STREONOR profiles and their device and page identifiers so you can select the right profile for stream controller setup or configuration.

Instructions

List STREONOR profiles and their device and page identifiers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only that the results include device and page identifiers, which is effectively return-value content already available via the existing output schema, and it discloses nothing about ordering, scope, 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.

Conciseness5/5

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

A single front-loaded sentence with no filler; the resource and the returned identifiers come first. Nothing could be trimmed without losing content.

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 zero-argument, read-only listing tool with full annotation coverage and an output schema, the description is essentially adequate. The remaining gap is the unexplained 'STREONOR' domain term and the vocabulary mismatch with the 'List Saved Scenes' title, which could confuse an agent about what is actually listed.

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?

Zero parameters, so the baseline applies and there is nothing for the description to disambiguate. The mention of 'device and page identifiers' is about output, not input.

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?

Specific verb ('List') plus resource ('STREONOR profiles') and the identifiers it returns ('device and page identifiers'). It is not, however, differentiated from siblings such as list_supported_devices or read_profile beyond the object it lists, and the opaque token 'STREONOR' carries no explanation, plus the annotation title 'List Saved Scenes' uses different vocabulary than 'profiles'.

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 when-to-use guidance and names no alternatives; nothing indicates how this differs from read_profile (single profile?) or the list_supported_devices sibling. Only the implied 'this is a listing call' is conveyed, with no prerequisites or exclusions.

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