DevTune MCP

devtune_get_audit_findings

Read-onlyIdempotent

Get audit findings and section assessments from the published Audit rollup, paged together from one shared offset: pagination.hasMore stays true while either has rows left, and the one that has run out returns an empty array on later pages. Section findings include exact excerpts, remedies, versions and coverage states; they do not change numerical scores.

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": "devtune_get_audit_findings"
  }
}

Input Schema

Name	Required	Description
`limit`	No	The same setting as pageSize. Send either.
`cursor`	No	pagination.nextCursor from the previous page, unchanged. Keep the other arguments the same; omit it for the first page.
`offset`	No	Deprecated: pass cursor instead. Zero-based result offset.
`pageSize`	No	Results per page (1-100). Defaults to 25.
`includeDismissed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / limit / $ref
```
Removed value: -"#/properties/pageSize"
```
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / limit / type
```
Added value: +"integer"
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedOct 25, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "pagination.nextCursor from the previous page, unchanged. Keep the other arguments the same; omit it for the first page.",
+  "maxLength": 1024,
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "$ref": "#/properties/pageSize",
+  "description": "The same setting as pageSize. Send either."
+}

addedInput schema / properties / offset / description

Added value: +"Deprecated: pass cursor instead. Zero-based result offset."

First observedSep 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description earns credit for going beyond them: it explains the merged pagination contract (shared offset, hasMore stays true while either stream has rows, exhausted stream returns an empty array). It also discloses that section findings do not change numerical scores, which is non-obvious read behavior an agent could otherwise misread.

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, both dense with information, with the primary purpose front-loaded and pagination behavior following. Every clause contributes something, though the pagination sentence is packed enough that it reads more like a spec than a guide.

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 does its share of describing return content (excerpts, remedies, versions, coverage states, hasMore, empty arrays on later pages). The main gap is includeDismissed, which is neither described here nor documented in the schema, so an agent must guess its effect.

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 coverage is 80%, so the baseline is 3 and the schema carries most of the parameter meaning. The description adds the useful clarification that both result types are paged from one shared offset, which affects how cursor is interpreted, but it says nothing about limit vs pageSize aliasing, the deprecated offset, or includeDismissed.

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 resource pair ('get audit findings and section assessments') and names the source ('the published Audit rollup'), so the agent knows exactly what data it retrieves. It does not explicitly contrast itself with siblings like devtune_get_audit_summary or devtune_get_audit_extraction, so the sibling differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the data it returns (findings and section assessments from a published rollup), and the pagination semantics tell the agent how to continue, but there is no explicit 'use this when…' or 'prefer X instead' guidance. An agent choosing among the many devtune_get_audit_* tools must infer the choice.

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

All DevTune MCP tools Inspect

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

Need Help?