Skip to main content
Glama

Fine Structure

by ai.finestructure
OverviewDiscussionsAdmin

Get Recommended Workflow

get_recommended_workflow
Read-onlyIdempotent

Return the recommended MCP tool sequence for a task type. Use this before creating apps, editing files, seeding data, publishing, setting up A/B tests, restoring versions, or configuring secrets/integrations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoOptional short description of the user's goal.
app_idNoOptional app ID. If provided, the workflow includes a safe app context summary.
task_typeNoThe task type to plan.unknown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / task_type / enum
      Previous value: -[
-  "ab_test",
-  "agency_client_app",
-  "create_app",
-  "direct_file_edit",
-  "domain_setup",
-  "edit_app",
-  "fix_runtime_error",
-  "generate_media",
-  "inspect_preview",
-  "publish_app",
-  "saas_setup",
-  "schema_change",
-  "secrets_integration",
-  "security_setup",
-  "seed_data",
-  "unknown",
-  "version_restore"
-]New value: +[
+  "ab_test",
+  "agency_client_app",
+  "backend_function",
+  "create_app",
+  "direct_file_edit",
+  "domain_setup",
+  "edit_app",
+  "fix_runtime_error",
+  "generate_media",
+  "inspect_preview",
+  "publish_app",
+  "saas_setup",
+  "schema_change",
+  "secrets_integration",
+  "security_setup",
+  "seed_data",
+  "unknown",
+  "version_restore"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / task_type / enum
      Previous value: -[
-  "ab_test",
-  "agency_client_app",
-  "create_app",
-  "direct_file_edit",
-  "domain_setup",
-  "edit_app",
-  "fix_runtime_error",
-  "inspect_preview",
-  "publish_app",
-  "saas_setup",
-  "schema_change",
-  "secrets_integration",
-  "security_setup",
-  "seed_data",
-  "unknown",
-  "version_restore"
-]New value: +[
+  "ab_test",
+  "agency_client_app",
+  "create_app",
+  "direct_file_edit",
+  "domain_setup",
+  "edit_app",
+  "fix_runtime_error",
+  "generate_media",
+  "inspect_preview",
+  "publish_app",
+  "saas_setup",
+  "schema_change",
+  "secrets_integration",
+  "security_setup",
+  "seed_data",
+  "unknown",
+  "version_restore"
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so no side-effect warning is needed. The description adds no behavioral detail beyond the annotations, such as behavior for the 'unknown' task_type, but it does not contradict them.

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?

Two compact sentences, front-loaded with the core purpose and followed by concrete use cases. There is no filler or redundant restatement of the title.

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 read-only, idempotent advisory tool with fully described optional parameters, the description covers what it returns and when to call it. It could be more explicit about the output structure or fallback when task_type is 'unknown', but nothing essential blocks correct invocation.

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 coverage is 100%, and each parameter already has a meaningful description, including the task_type enum and default. The tool description does not add parameter-level detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies exactly what is returned ('recommended MCP tool sequence') and the input dimension ('task type'), which is a specific verb+resource statement. This output is distinct from the execution-focused sibling tools and is reinforced by the 'Use this before...' planning context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the situations where the tool should be used before: creating apps, editing files, seeding data, publishing, A/B tests, version restore, and secrets/integrations. It does not mention exclusions or alternative tools, so it falls just short of a 5.

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

All Fine Structure toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources