Skip to main content
Glama

Detect app type

detect
Idempotent

Classify this project through Tofu’s shared safety and deployment backend. mobileReadiness is static metadata, not a safety or device verdict.

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": {
      "projectId": "<projectId>"
    },
    "name": "detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stackYes
evidenceYes
frameworkNo
scannedFilesYes
mobileReadinessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Against annotations that already declare idempotent=true, destructive=false and openWorldHint=false, the description adds some context: the classification runs through a shared backend and mobileReadiness is static metadata rather than a safety or device verdict, which usefully prevents misreading the output. However, it never addresses readOnlyHint=false for what sounds like a pure detection call, so the agent cannot tell whether state is written or cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, but the second sentence introduces "mobileReadiness" with no setup, so the caveat reads as a fragment detached from any explained return value. Front-loading of the core purpose is acceptable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 spelled out, but for a tool whose result gates safety and deployment decisions the description leaves the classification categories, the implication of readOnlyHint=false, and the meaning of projectId unaddressed. It is thin relative to the stakes implied by the text.

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 0% for the single required projectId parameter, and the description only alludes to "this project" without defining the identifier's format or scope. It does not compensate for the undocumented parameter.

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

Purpose3/5

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

"Classify this project" gives a verb and a resource, but the classification target (an app type) is only inferable from the title, not stated in the description. The mention of "Tofu's shared safety and deployment backend" adds flavor without clarifying what the tool produces, and nothing distinguishes it from any sibling.

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?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives among the many app* configuration siblings. The agent must guess whether this is a prerequisite step before deployment or an optional diagnostic.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources