Skip to main content
Glama

Victano: EU tenders and grant calls

by com.victano
OverviewDiscussionsAdmin

Who am I, and what is left

whoami
Read-onlyIdempotent

The connected account: tier, persona, corpus freshness, and every limit — what is left in the current window, and the caps that do not renew. Call it when a user asks about limits, when you are unsure whether you are authenticated, or to confirm a setting took.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description is not burdened with basic safety disclosure. It adds useful behavioral detail by enumerating what the response reports: tier, persona, corpus freshness, current window limits, and non-renewing caps. No contradiction with 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 two sentences with no filler. The first sentence front-loads the core output value, and the second sentence gives concrete invocation scenarios. Every clause contributes actionable information.

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?

For a simple read-only tool with one optional, fully documented parameter and no output schema, the description covers purpose, triggering conditions, and key return content. It omits explicit mention of the 'session' parameter in the description, but the schema already covers that, so the combined context is sufficient.

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 100%, so the session parameter is fully documented in the schema. The description itself adds no param-specific semantics beyond the schema, and with full coverage the baseline of 3 applies.

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 specifies the tool returns details about the connected account: tier, persona, corpus freshness, and limits. It clearly identifies the resource and the kind of information, though it lacks an explicit verb like 'retrieve' or 'return'. The sibling tools handle workflows and opportunities, so the account-focus differentiates it adequately.

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 explicit trigger conditions: call it when a user asks about limits, when unsure about authentication, or to confirm a setting took effect. It does not explicitly mention when not to use it or name alternatives, but the provided context is clear and practical for an agent.

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