Skip to main content
Glama

profile_target_vibe

Detects and reports host project coding conventions—language, module system, casing, indentation, quotes, semicolons, and error-handling idiom—so generated or adapted code matches the existing style.

Instructions

Profiles the host project conventions (language, module system, camelCase/snake_case/PascalCase, indentation, quotes, semicolons, error-handling idiom).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "profile_target_vibe"
  }
}

Input Schema

NameRequiredDescriptionDefault
sampleCodeNo
workspacePathNo
explicitLanguageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the analytical dimensions it examines, which implies a read-only inspection of project files, but it never states whether files are written, whether a workspacePath is required, what happens when no inputs are supplied, or what the caller receives back. Coverage is partial rather than misleading.

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?

A single front-loaded sentence with the key purpose first and the detail compressed into an efficient parenthetical list. Nothing is redundant, though the dense list substitutes for structured sections on inputs and output.

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?

With zero annotations, no output schema, and three entirely undocumented optional parameters, the definition should explain the precedence between explicitLanguage and auto-detection, minimum viable inputs, and the shape of the result. None of that is present, leaving an agent unable to decide what to pass when calling it.

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% across three parameters (sampleCode, workspacePath, explicitLanguage), so the description needed to compensate and instead mentions none of them. It never explains how explicitLanguage's enum overrides detection, what sampleCode contributes, or that all three are optional. The enumeration of detected conventions touches on language detection but maps to no parameter.

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?

The description names a specific verb ('profiles') and a specific resource ('host project conventions'), then enumerates the exact conventions detected: language, module system, casing style, indentation, quotes, semicolons, and error-handling idiom. That detail clearly separates it from siblings like synthesize_chameleon_graft or verify_engine_parity. It loses a point only because 'profiles' leaves the output nature (report vs. mutation) ambiguous.

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 statement, no prerequisite, and no named alternative or sequencing hint relative to siblings such as synthesize_chameleon_graft. An agent must infer from the tool name alone that this is a discovery step that should precede patch synthesis. No exclusions or fallback conditions are given.

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