Skip to main content
Glama
Sign In

Roar AI

by com.roar-ai
OverviewDiscussionsAdmin

Detect how a repository would be built

detect_repo_framework
Read-onlyIdempotent

Show the framework the builder detects in a GitHub repository, or in one folder of it, and the install, build and start commands it would use. Read this before deploying an unfamiliar repository: a repository detected as the wrong framework fails in ways that look like bugs in the app. Free, and changes nothing.

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": {
      "repo": "<repo>"
    },
    "name": "detect_repo_framework"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name, from list_github_repos
branchNoDefaults to the repo default branch
rootDirNoA folder from list_repo_app_folders

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds information the annotations do not carry: that the call is free (no cost implication) and the downstream failure mode when detection is skipped. Return shape (commands) is only sketched, not detailed.

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?

Two sentences, front-loaded with the outcome and followed by the motivating guidance; no filler or hedging. The closing 'Free, and changes nothing' partially duplicates readOnlyHint/destructiveHint, which keeps it just short of ideal.

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?

With no output schema, the description still tells the agent what comes back (framework and the three command types), and it covers the precondition for calling (unfamiliar repo before deploy). Nothing critical is missing for a read-only, single-purpose inspector.

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 100%, so repo (owner/name), branch (defaults to repo default) and rootDir (a folder) are already documented in the schema. The phrase 'or in one folder of it' only restates rootDir, so the description adds essentially nothing beyond structured fields; baseline 3 applies.

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 and outcome: it shows the detected framework plus the install, build and start commands the builder would use, optionally scoped to a single folder. That is concrete enough to distinguish it from describe_repo or check_repo_build by intent, but no sibling is named explicitly.

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?

Gives a clear usage condition — 'Read this before deploying an unfamiliar repository' — with a motivating consequence (misdetection 'fails in ways that look like bugs in the app'). It lacks explicit when-not guidance or a named alternative for repositories you already know well.

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

All Roar AI toolsInspect
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