Skip to main content
Glama

netcafe-devkit

by com.ainetcafe

What changed between two texts, line by line

diff_text
Read-onlyIdempotent

Returns which lines were added and which were removed, with line numbers — computed with a longest-common-subsequence, not guessed by a model. Use to compare two versions of a config, a document, or any command output, instead of asking an LLM to eyeball two blobs and hoping it notices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYesThe first (before) text.
bYesThe second (after) text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds that the diff is computed via LCS, not guessed, conveying determinism and accuracy. This is valuable beyond annotations, though it doesn't cover potential edge cases.

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?

Two sentences, front-loaded with the primary function, followed by usage context. No wasted words or repetition of schema information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-string tool with an output schema present, the description covers purpose, usage, and behavioral expectations completely. The existence of an output schema means return format details are already handled structurally.

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%, and each parameter has a clear description ('first (before) text' and 'second (after) text'). The description adds no further semantic detail beyond what the schema provides, so a baseline score of 3 is appropriate.

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 exactly what the tool does: returns added and removed lines with line numbers, using LCS. It clearly identifies the resource (two texts) and the operation (diff calculation), distinguishing it from any sibling tool.

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

Usage Guidelines5/5

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

Explicitly tells when to use it: 'Use to compare two versions of a config, a document, or any command output.' It also explains the alternative (asking an LLM) and why this tool is better, providing clear guidance on when to choose this tool.

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

All netcafe-devkit toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have clear, separate purposes: diff, redact, regex, JWT, SQL, timezone, units, QR, screenshot. The main overlap is between json_format and validate_json, since both parse and validate JSON, though their outputs differ enough to be workable.

Naming Consistency4/5

The majority follow a clear snake_case verb_noun or noun_verb pattern like diff_text, transpile_sql, and timezone_convert. sql_from_description and what_can_you_do break the pattern, but the rest is predictable and readable.

Tool Count5/5

14 tools is well-scoped for a general-purpose developer utility server. Each tool covers a distinct practical need, and the count does not feel bloated for the breadth of features offered.

Completeness4/5

The toolkit covers a broad range of everyday dev utilities: text diffing, redaction, regex, JSON/YAML, SQL, time, units, JWT, QR, and screenshots. Some common basics like base64, hashing, or URL encoding could be useful additions, but the surface is complete enough for its stated purpose.

Resources