Skip to main content
Glama

FLOCORE Governed MCP

by tech.flocore
OverviewDiscussionsAdmin

Request governance onboarding

flocore_onboard_request

Registers an onboarding request for human review (human-gated approval, Ed25519 signed receipts, EU AI Act Article 12 audit evidence). Public: no token needed. Returns a request id and a sandbox token (fc_test_...) immediately, to rehearse the loop; a live token is issued only after a person approves the application. Set rehearsal_only to true to get a sandbox token without applying.

Input Schema

NameRequiredDescriptionDefault
orgNooptional: the organisation the agent acts for
agentYesyour agent name or identifier
sourceNooptional: where you found us, for example a registry or the pitch (letters, digits, dots and dashes)
public_keyNooptional: your agent's own Ed25519 PUBLIC key, raw 32 bytes as base64url or a public JWK as JSON text. Give it and, once a human approves you, your token is bound to it and your key's thumbprint appears on your signed receipts. Never send a private key.
referred_byNooptional: the governed agent or partner that sent you here (recorded as the referral)
intended_useNooptional: what world-affecting actions you want governed
jurisdictionNooptional: the legal jurisdiction that brought you here, a code from the Advatar pitch (eu, coe, za, kr, us, vn, ng, ke, mx, oecd). Recorded so we learn which law matters to builders
owner_contactNothe email address of the person who owns the agent, so a person can approve it and be sent its token (required unless rehearsal_only is true)
rehearsal_onlyNooptional: true to get ONLY a sandbox token to rehearse the approval loop. Nothing is registered, no email is sent and no one is asked to review anything. Limits: 3 per hour per connection. To apply for real, call again without it and give owner_contact

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / owner_contact / description
      Previous value: -"an email or handle we can reach to confirm onboarding"New value: +"the email address of the person who owns the agent, so a person can approve it and be sent its token (required unless rehearsal_only is true)"
    • addedInput schema / properties / rehearsal_only
      Added value: +{
+  "description": "optional: true to get ONLY a sandbox token to rehearse the approval loop. Nothing is registered, no email is sent and no one is asked to review anything. Limits: 3 per hour per connection. To apply for real, call again without it and give owner_contact",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "agent",
-  "owner_contact"
-]New value: +[
+  "agent"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / referred_by / description
      Previous value: -"optional: the governed agent or partner that sent you here (so credit flows to whoever brought you)"New value: +"optional: the governed agent or partner that sent you here (recorded as the referral)"
  3. Changed2 schema fields changed
    • addedInput schema / properties / jurisdiction
      Added value: +{
+  "description": "optional: the legal jurisdiction that brought you here, a code from the Advatar pitch (eu, coe, za, kr, us, vn, ng, ke, mx, oecd). Recorded so we learn which law matters to builders",
+  "type": "string"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "description": "optional: where you found us, for example a registry or the pitch (letters, digits, dots and dashes)",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / public_key
      Added value: +{
+  "description": "optional: your agent's own Ed25519 PUBLIC key, raw 32 bytes as base64url or a public JWK as JSON text. Give it and, once a human approves you, your token is bound to it and your key's thumbprint appears on your signed receipts. Never send a private key.",
+  "type": "string"
+}
  5. Changed1 schema field changed
    • addedInput schema / properties / referred_by
      Added value: +{
+  "description": "optional: the governed agent or partner that sent you here (so credit flows to whoever brought you)",
+  "type": "string"
+}
  6. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare the generic safety profile (readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false). The description goes well beyond that: human-gated approval, Ed25519 signed receipts, EU AI Act Article 12 audit evidence, the fact that a live token is issued only after a person approves, and the 3-per-hour rehearsal rate limit. That is exactly the kind of behavioral context annotations cannot carry.

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?

Front-loads the core action and the immediate return value, then handles the rehearsal variant. Dense with parentheticals but each sentence carries distinct information; slightly packed, though nothing is genuinely redundant.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden — and it does: a request id plus an fc_test_ sandbox token immediately, with a live token only after human approval. Combined with the auth note ('no token needed') and the approval gating, an agent has everything needed to call this correctly.

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 schema already documents all nine parameters in detail. The description reinforces the owner_contact/rehearsal_only dependency and names the sandbox token prefix (fc_test_...), but adds little syntax or constraint information beyond what the schema already states. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Registers an onboarding request for human review') and immediately distinguishes itself from siblings by describing a registration/approval flow rather than inspection, verification, or support. An agent can tell what this tool does without opening the schema.

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 clear operational context: 'Public: no token needed', and explicitly routes between two modes — 'Set rehearsal_only to true to get a sandbox token without applying' versus applying for real with owner_contact. It does not, however, contrast itself against the sibling tools (aegis_inspect, flocore_verify_counterparty), so the when-not-to-use case is left implicit.

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

All FLOCORE Governed MCP 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