Skip to main content
Glama
Sign In

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

by com.datailo
OverviewDiscussionsAdmin

Tool schema

datailo_tool_schema
Read-onlyIdempotent

Sign-in required: call datailo_connect(email) and datailo_connect_verify first (free, one email) unless this connection is already signed in. The full input schema for one tool of an enabled service, and how to call it.

Input Schema

NameRequiredDescriptionDefault
toolYes
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.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the auth flow and a hint at the return content ('full input schema ... and how to call it'). It adds real context beyond the structured fields and contradicts nothing, but says nothing about returned schema size or limits.

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 with the blocking prerequisite front-loaded, which is the most important thing for an agent to read first. The auth instruction is long but load-bearing; minimal waste.

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

Completeness3/5

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

There is no output schema, and the description does at least signal what is returned (the input schema plus call instructions) and how to authenticate. It omits how to discover valid service/tool identifiers and any caveats about the returned schema, leaving gaps for a lookup-style tool.

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 only 33%: 'session' is documented in the schema itself, but 'tool' and 'service' are bare strings. The description partially compensates by implying the service must be enabled and the tool belongs to it, yet it never says where to obtain valid names or whether they must match datailo_tools output.

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 concrete resource: 'the full input schema for one tool of an enabled service, and how to call it.' An agent can distinguish it from the listing siblings (datailo_tools, datailo_catalog) by its schema-retrieval role, though no sibling is named explicitly.

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?

Gives an explicit conditional prerequisite: sign in via datailo_connect(email) and datailo_connect_verify 'unless this connection is already signed in.' That is clear when-to-use guidance. It does not, however, say when to prefer this over datailo_tools, datailo_describe, or datailo_invoke.

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