Skip to main content
Glama

Victano: EU tenders and grant calls

by com.victano
OverviewDiscussionsAdmin

Get the full record for one opportunity

get_opportunity
Read-onlyIdempotent

Full normalised record plus the document inventory. Use before advising on a bid; a search card is not enough. Follow with read_document for eligibility text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
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.
as_unitsNoAlso return the notice as text units (title, notice); for verifiers.
opportunity_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as_units
      Added value: +{
+  "default": false,
+  "description": "Also return the notice as text units (title, notice); for verifiers.",
+  "title": "As Units",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • 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."
  3. 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"
+}
  4. First observed

TDQS

A3.6/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, closed-world), so the bar is lower. The description still adds value beyond them by describing what is returned (normalised record + document inventory) and the intended sequence into read_document.

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?

Three short, front-loaded sentences with no filler; scope is stated first, then usage, then the follow-up. Slightly terse phrasing ('a search card is not enough') costs it a point but nothing is wasted.

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?

For a read-only tool with no output schema, the description adequately covers the return shape and the workflow handoff. It leaves a real gap around which identifier parameter to supply, which matters given two ambiguous undocumented id fields.

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 coverage is only 50% and the description says nothing about any of the four parameters. In particular, 'id' and 'opportunity_id' are both undocumented nullable strings with overlapping meaning, and the description gives no help in disambiguating them or in explaining session/as_units.

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 the specific resource and scope: the full normalised record for one opportunity plus its document inventory. The clause 'a search card is not enough' implicitly contrasts with search_opportunities, though it never names that sibling 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 a clear trigger ('Use before advising on a bid') and a follow-up step ('Follow with read_document for eligibility text'), which is genuine routing guidance. It stops short of naming search_opportunities as the explicit alternative or stating any when-not conditions.

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