Skip to main content
Glama

Datailo: one MCP connection to tenders, EU regulation and law

by com.datailo
OverviewDiscussionsAdmin

Search tools

datailo_tools
Read-onlyIdempotent

Search the tools of your enabled services (read live from each service). q takes words or a whole sentence: tools are ranked by the words they match, name and title first. service narrows to one service; include_available also previews services you could enable; limit caps the list (default 50).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
limitNo
serviceNo
sessionNoThe `session` value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key.
include_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / session / description
      Previous value: -"The `session` value datailo_connect_verify returned, when this client keeps no connection session. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key."New value: +"The `session` value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key."
  2. Changed1 schema field changed
    • addedInput schema / properties / session
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The `session` value datailo_connect_verify returned, when this client keeps no connection session. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key.",
+  "title": "Session"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds behavioral details like 'read live from each service' and ranking behavior, which is useful. However, it doesn't mention potential latency or that results depend on enabled services, leaving some gaps. It does not contradict 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 a single sentence that packs all essential information without fluff. It is front-loaded with the core purpose, followed by parameter details. Every clause adds value, and it is appropriately concise for a search tool.

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?

The tool is moderate in complexity with 5 optional parameters and no output schema. The description covers most aspects, but it doesn't explicitly state that the session parameter should be passed as per the schema, nor does it mention pagination or result format. However, given the annotations and schema, it is mostly complete for an agent to call it correctly.

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 only 20%, so the description must add meaning for the parameters. It does explain q, service, include_available, and limit, but the 'session' parameter is only described in the schema, not in the description. The description adds value for most parameters but misses the session parameter, which is critical for authentication in context.

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 that this tool searches tools from enabled services, using a query 'q' that can be words or a sentence. It distinguishes its purpose from siblings like datailo_describe or datailo_tool_schema by focusing on search across services, and it explicitly mentions ranking by matched words with name and title first.

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 explains how to use the tool: q takes words or a sentence, service narrows to one service, include_available previews additional services, and limit caps the list. It doesn't explicitly say when to use this instead of other tools, but the purpose is clear enough that an agent can infer it for discovery tasks. It lacks explicit exclusions or alternatives, but the context is strong.

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

All Datailo: one MCP connection to tenders, EU regulation and law toolsInspect
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