Skip to main content
Glama

OwnYourAgent

Prepare an OwnYourAgent request link

prepare_intake_link
Read-onlyIdempotent

Returns a link to the OwnYourAgent request form (the agreement sheet (afsprakenkaart) as a form) with the chosen starting phase, topic and, optionally, Ownership Check IDs pre-filled. It contains no personal data and submits nothing: the person opens the link, checks the answers, adds their own contact details and sends it themselves. Use it when the user wants to ask OwnYourAgent for a proposal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prepare_intake_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the form: nl (default) or en.nl
phaseNoStarting phase: kansenrapport (AI opportunity report), pilot, implementatie (implementation) or beheer (management).
topicNoThe work the agent should help with: facturen (invoices and orders), klantvragen (customer questions), telefoon (phone), kennis (internal knowledge), offertes (quotations) or anders (other).
check_idsNoOptional Ownership Check IDs (from get_ownership_check) the user wants OwnYourAgent to review, e.g. ["E-02","E-03"].

Output Schema

NameRequiredDescriptionDefault
urlYes
langYes
noteYes
phaseYes
topicYes
check_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint/idempotentHint, the description discloses the non-obvious behavior: the tool submits nothing, contains no personal data, and the recipient must open the link, verify the answers, add their own contact details and send it themselves. This is exactly the context an agent needs to set user expectations before and after the call.

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?

Three short sentences: what it returns, what it does not do, and when to use it. The most safety-relevant fact (nothing is submitted) is front-loaded and nothing is repeated from the schema or annotations.

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?

With an output schema present, return values need no explanation, and the description still covers the one thing the schema cannot: that the produced link is inert and depends on a human to complete it. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, and the description earns above it by explaining the effect of the parameters: phase, topic and check_ids are pre-filled into the link, which tells the agent these are seeding values rather than filters. The lang parameter is left unaddressed, though the schema documents it.

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?

The description names a specific verb and artifact: it returns a link to the OwnYourAgent request form (the agreement sheet rendered as a form). It also states exactly what is encoded in the link (starting phase, topic, optional Ownership Check IDs), which lets an agent distinguish it from siblings like get_ownership_check or get_agreement_card_template.

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?

It gives a clear trigger: 'Use it when the user wants to ask OwnYourAgent for a proposal.' That is enough to select the tool in context. It stops short of explicit exclusions or naming the alternative path (e.g., gathering check IDs via get_ownership_check first), so it is not a full when/when-not statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources