Skip to main content
Glama

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

by com.datailo
OverviewDiscussionsAdmin

Enable a service

datailo_enable
Idempotent

Enable a federated service on your Datailo account. For services with an account model the hub links (or creates) your account there by your email and keeps an encrypted key; keyless services are enabled as a trial. Then datailo_tools and datailo_invoke reach it through this one connection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planNo
serviceYes
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.

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

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses meaningful side effects: the hub links or creates an external account by email, stores an encrypted key, and enables keyless services as a trial. This gives the agent useful behavioral context about account linking and credential handling that annotations alone do not provide.

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 compact and front-loaded: purpose first, behavioral detail second, downstream consequence third. Every sentence contributes useful information and there is no filler.

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

Completeness2/5

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

For a tool with no output schema and low parameter coverage, the description is incomplete. It does not explain what the tool returns, how to populate 'plan', where to find valid 'service' identifiers, or what the 'session' parameter is for, leaving important gaps for an agent trying to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, and the description does not compensate. It gives context for the 'service' concept but never explains acceptable values for 'service' or the meaning of 'plan', and it omits 'session' entirely even though the schema documents that parameter.

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 opens with a specific verb and resource: 'Enable a federated service on your Datailo account.' It also distinguishes itself from siblings by explaining that datailo_tools and datailo_invoke will reach the enabled service through this connection, clarifying the tool's role relative to related operations.

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?

The description implies when to use the tool: it is the prerequisite that lets datailo_tools and datailo_invoke reach a service. However, it does not explicitly state when to prefer this over siblings like datailo_connect or datailo_disable, and it offers no exclusions or alternative conditions.

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