Skip to main content
Glama
Sign In

NoBrainer Tech Flow

by io.github.nobrainer-tech
OverviewDiscussionsAdmin

Recommend Flow model

recommend_flow_model
Read-onlyIdempotent

Use when picking a model for a Flow task: top-3 from a pinned NoBrainer benchmark snapshot, no invented scores.

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": {
      "task": "<task>"
    },
    "name": "recommend_flow_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
haveNoProviders, models or client apps you can use
roleNo
taskYes
priorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds meaningful context beyond that: results are capped at three, sourced from a pinned benchmark snapshot, and scores are not fabricated — which tells the agent the data is fixed and citation-backed rather than generated.

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?

One front-loaded sentence with the trigger first and the result shape second; no filler or repetition. It is efficient, though the extreme terseness leaves little room for the parameter explanation this schema needs.

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?

It covers the trigger, the output cardinality, and data provenance, which is the core of a recommendation tool. With no output schema and only 25% parameter coverage, however, an agent still lacks guidance on the three enum parameters and on how `have` interacts with the recommendation.

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 only 25% (only `have` is documented), and the description does not compensate: it never explains what `role` (main vs worker) changes, how `priority` (quality/balanced/efficient) trades off, or how `have` constrains the candidate set. Only `task` is loosely implied by "for a Flow task", leaving three parameters to be guessed from enum values alone.

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 action and output: it recommends a model for a Flow task, returning the top-3 from a pinned NoBrainer benchmark snapshot. That is concrete enough for an agent to know exactly what comes back, though it never explicitly says how it differs from the other Flow-related siblings (which do not appear to offer model selection).

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?

"Use when picking a model for a Flow task" gives an explicit trigger condition, which is the key routing signal an agent needs. It does not state when NOT to use it or name an alternative, but no sibling appears to overlap, so the guidance is clear for the main case.

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

All NoBrainer Tech Flow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources