Flowlines - MCP Analytics

List agent attributes

list_agent_attributes

Read-onlyIdempotent

List observed attributes for an agent in a Flowlines namespace.

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": {
      "reason": "<reason>",
      "user_intent": "<user_intent>",
      "namespace_id": "<namespace_id>",
      "agent_name": "<agent_name>"
    },
    "name": "list_agent_attributes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size. Defaults to 20.
`reason`	Yes	A short phrase saying why you are calling this tool, for example: find unpaid invoices.
`search`	No
`agent_name`	Yes	Exact agent name returned by list_agents.
`user_intent`	Yes	One sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.
`namespace_id`	Yes	Flowlines namespace UUID.

Output Schema

Name	Required	Description	Default
`data`	Yes
`notice`	No
`truncation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful nuance that these are "observed" attributes (versus configured), but says nothing about pagination ordering or result completeness, so a 3 is appropriate.

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?

A single front-loaded sentence with zero filler. It is appropriately sized for a simple read tool, though it is arguably too terse to be maximally helpful.

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?

An output schema exists, so return values needn't be described. However, the description omits pagination semantics (limit defaults to 20, max 50) and the presence of a search filter, which are relevant for invoking this list tool 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 description coverage is 83%, so the schema already documents limit, agent_name, reason, user_intent and namespace_id. The description adds no meaning for the search parameter or pagination behavior, leaving the baseline 3.

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?

States a specific verb+resource ("List observed attributes") scoped to an agent within a Flowlines namespace, so the agent can tell it apart from generic siblings like list_agents or list_signals. It does not explicitly contrast itself with those siblings, which holds it below a 5.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as list_agents (to resolve the agent_name) or get_signal. Usage is only implied by the tool name.

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

All Flowlines - MCP Analytics tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?