devflow

by cocaxcode

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

df_issue

Fetch complete Jira issue details by issue key (e.g., PROJ-123). Read-only operation without side effects.

Instructions

Obtener el detalle completo de un issue de Jira. Solo lectura, sin efectos secundarios.

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": {
      "issueKey": "<issueKey>"
    },
    "name": "df_issue"
  }
}

Input Schema

Name	Required	Description	Default
`issueKey`	Yes	Clave del issue (ej: PROJ-123)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Sep 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and explicitly discloses that the operation is read-only and has no side effects. This is valuable safety information for an agent, though it does not mention auth requirements or error behavior.

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?

The description is one short, front-loaded sentence followed by a safety qualifier. Every word contributes value and there is no redundancy.

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 simple single-parameter read-only tool, the description is nearly complete. It conveys the operation, scope, and safety profile, though the absence of an output schema means 'detalle completo' is somewhat undefined.

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?

The single parameter issueKey is fully documented in the input schema with an example format. Since schema description coverage is 100%, the description does not need to add parameter details, and it does not.

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 states a clear verb and resource: obtain the full detail of a single Jira issue. It distinguishes itself from siblings like df_issues by conveying that this tool targets one specific issue's complete detail, not a list.

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?

The description gives clear context for use: when you need the complete detail of one Jira issue. It does not explicitly name alternatives or exclusions, but the read-only note and singular scope make the applicable use case clear.

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