Skip to main content
Glama

Victano: EU tenders and grant calls

by com.victano
OverviewDiscussionsAdmin

List the available playbooks

list_workflows
Read-onlyIdempotent

The playbook library: how bid professionals actually run this work, from the weekly scan through qualification, eligibility screening, reading a specification, clarification questions, and the proposal skeleton. READ A WORKFLOW BEFORE IMPROVISING A PROCESS. Whole jobs (jobs) come first. Pass persona='consultant' to see the multi-client ones. Follow with get_workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many playbooks to list (jobs always lead); default all.
detailNo'compact' (default) or 'full'.
personaNo
sessionNoThe `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key.
max_charsNoHard cap on the answer's size in characters (default 8000). Over it, cards shrink to the essentials, then rows are dropped from the end, and `truncated` says how to get the rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "'compact' (default) or 'full'.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "title": "Detail"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "How many playbooks to list (jobs always lead); default all.",
+  "title": "Limit"
+}
    • addedInput schema / properties / max_chars
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Hard cap on the answer's size in characters (default 8000). Over it, cards shrink to the essentials, then rows are dropped from the end, and `truncated` says how to get the rest.",
+  "title": "Max Chars"
+}
    • changedInput schema / properties / session / description
      Previous value: -"The `session` value connect_verify returned, when this client keeps no connection session. Pass it on every Victano call in this conversation; omit it when the user connected with Sign in (OAuth) or a key."New value: +"The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key."
  2. Changed1 schema field changed
    • addedInput schema / properties / session
      Added value: +{
+  "description": "The `session` value connect_verify returned, when this client keeps no connection session. Pass it on every Victano call in this conversation; omit it when the user connected with Sign in (OAuth) or a key.",
+  "type": "string"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive, so the description's main value is in adding ordering behavior ('Whole jobs come first'), persona-based filtering, and a next-step recommendation. No contradiction with annotations; the description complements them with practical behavioral details.

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, efficiently packed with context and instructions. The initial clause about bid professionals is a bit verbose but sets the scene; the imperative 'READ A WORKFLOW BEFORE IMPROVISING A PROCESS' is impactful. No fluff, and key instructions are front-loaded.

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?

Given the tool's simplicity (0 required params, no output schema) and annotations covering safety, the description covers purpose, usage timing, ordering, a specific filter, and the next step. It does not explain return format, but that is not essential for a listing tool with optional params.

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

Parameters4/5

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

Schema description coverage is 80%, so the baseline is 3. The description adds meaning for the persona parameter ('Pass persona='consultant' to see the multi-client ones'), which is otherwise undocumented in the schema. It does not add for other params, but this single addition pushes it above baseline.

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?

The description makes the tool's purpose clear: it lists playbooks, as evidenced by 'The playbook library...' and the instruction to 'Follow with get_workflow', implying a list-then-read sequence. It does not explicitly contrast with siblings like search_opportunities, but the reference to get_workflow as the next step helps differentiate from that tool.

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 gives strong usage direction: 'READ A WORKFLOW BEFORE IMPROVISING A PROCESS' establishes when to use it, and 'Pass persona='consultant' to see the multi-client ones' specifies a conditional filter. It also tells the agent to follow with get_workflow, though it does not explicitly state when not to use the tool.

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

All Victano: EU tenders and grant calls 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