Lists flow diagrams saved in a project and returns each diagram's index so you can reference the correct diagram in later calls.
List the flow diagrams saved in a project, with their index. Use the index to refer to a diagram.
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes |
Changes observed during successful MCP inspections.
v1.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden itself. It implies a read-only listing and confirms the return includes an index per diagram, but it says nothing about pagination, ordering, empty-project behavior, or access permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded, with the index semantics stated immediately after the action. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read tool with no output schema, the description covers the action and the key return concept (index). It could say a bit more about what each listed entry contains, but it is adequate to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is one required parameter (projectId) with 0% schema description coverage, so the description must compensate. Phrasing it as 'saved in a project' does tie the parameter to a project, but it adds no detail on ID format or source.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource ('List the flow diagrams saved in a project'), which clearly distinguishes it from siblings like delete_flow, map_user_flow and list_projects. It doesn't explicitly name or contrast a sibling, which keeps it at 4.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Use the index to refer to a diagram' implies the intended follow-up workflow, so usage is inferable. However there is no explicit guidance on when to pick this over alternatives (e.g. list_projects or map_user_flow) and no stated prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.