Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

read_profile

Read-only

Retrieve a profile or page's existing actions, settings, and content hash to inspect the current STREONOR controller configuration before editing.

Instructions

Read a profile or page including its existing actions, settings, and content hash.

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": {
      "profile": "<profile>"
    },
    "name": "read_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
profileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds useful content about what is returned (actions, settings, content hash), but says nothing about behavior on a missing profile, permissions needed, or why the content hash matters (likely optimistic concurrency).

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?

One front-loaded sentence with no filler; the resource and the returned content are stated immediately. Nothing in the wording is redundant.

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

Completeness3/5

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

With only two parameters and no output schema, the description is nearly sufficient, and annotations cover the safety profile. However, the unexplained optional page parameter and the unexplained content hash leave real gaps for a tool that is the natural entry point to the apply/preview workflow.

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

Parameters2/5

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

Schema description coverage is 0% and both properties carry only bare titles ("Profile", "Page") with the page defaulting to an empty string. The phrase "profile or page" hints that page narrows the read, but the description never explains the relationship, whether page is optional, or what the empty default means.

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 uses a specific verb ("Read") on a specific resource ("a profile or page") and enumerates what is retrieved: existing actions, settings, and content hash. That distinguishes it from mutation siblings like apply_scene_change and preview_* tools, though it never explicitly contrasts with list_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?

There is no stated when-to-use, when-not-to-use, or named alternative. An agent must infer that this is the inspection step preceding preview/apply tools, and nothing tells it whether to use read_profile versus list_profiles for discovery.

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