Skip to main content
Glama

AI NetCafé

by com.ainetcafe

Two tables → what differs (the VLOOKUP job, no amounts needed)

diff_tables
Read-onlyIdempotent

Matches rows across two CSVs on a key column and reports three things: keys only in A, keys only in B, and keys in both whose other columns disagree — naming the exact column and both values. Unlike reconcile_ledger this needs no amount column, so it also fits name lists, inventory counts, permission tables, and any "these two exports should match" check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesColumn that identifies a row, e.g. id.
url_aNoLink to the first CSV.
url_bNoLink to the second CSV.
text_aNoOr the first CSV content directly.
text_bNoOr the second CSV content directly.

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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context beyond these by explaining the exact matching semantics and that it reports which column differs and both values. No contradictions with annotations.

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 two sentences, front-loaded with the core purpose, then followed by usage guidance. Every sentence earns its place, with no filler or repetition.

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?

The tool has an output schema, so return values are already specified. The description provides all necessary operational context: the matching algorithm, output categories, and appropriate use cases. It is fully complete for the tool's complexity.

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%, with each parameter clearly described (e.g., 'Column that identifies a row', 'Link to the first CSV'). The tool description does not need to add parameter-level detail since the schema already does the heavy lifting.

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 clearly states the verb 'Matches rows across two CSVs on a key column' and specifies the exact three outputs (keys only in A, only in B, and mismatches with column names and values). It also distinguishes itself from the sibling reconcile_ledger by explicitly noting it needs no amount column.

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?

The description explicitly says 'Unlike reconcile_ledger this needs no amount column' and lists appropriate use cases ('name lists, inventory counts, permission tables, and any "these two exports should match" check'). This provides clear when-to-use guidance and names an alternative.

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

All AI NetCafé 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.9/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose with detailed descriptions that explicitly differentiate even close pairs like diff_tables vs reconcile_ledger and list_models vs model_costs. No two tools appear to do the same thing, and the what_can_you_do tool further resolves any confusion.

Naming Consistency3/5

The majority of tools follow a verb_noun snake_case pattern (build_app, fetch_page, list_tasks), but several notable deviations exist: ai_visibility, china_reachability, model_costs, json_yaml, pdf_to_markdown, what_can_you_do, recall, remember, and jwt_decode. This mixed convention, while still readable, is not fully consistent.

Tool Count3/5

With 34 tools, the count is high and exceeds the typical comfortable range for an MCP server. However, the server is a broad AI utility platform covering web, data, LLM, conversion, and scheduling tasks, and each tool appears to serve a distinct purpose with little redundancy, making the large but organized set borderline appropriate for its scope.

Completeness3/5

The tool surface covers a wide array of common workflows (search, fetch, table operations, PDF extraction, model comparisons, task scheduling, memory). However, check_job references deep_research, translate_pdf, and make_slides which are not present in the tool list, and there is no update tool for tasks/apps or a way to delete memories, leaving some user journeys incomplete.

Resources