OwnYourAgent Agentvoordeur

Get the agreement sheet (afsprakenkaart) template

get_agreement_card_template

Read-onlyIdempotent

Returns the agreement sheet (afsprakenkaart): the agreements per engagement that OwnYourAgent puts in writing before building an agent. Sections 1-5 (where the data is, what the agent may do, when a person decides, what the client owns, how the client continues without OwnYourAgent), the three starting levels, the ten-question exit test to ask any vendor, and a JSON Schema of the template. Not legal advice.

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": "get_agreement_card_template"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the returned text: nl (Dutch) or en (English). Omit to get both.

Output Schema

Name	Required	Description	Default
`url`	Yes
`name`	Yes
`status`	Yes
`exitTest`	Yes
`sections`	Yes
`generated`	Yes
`disclaimer`	Yes
`jsonSchema`	Yes
`description`	Yes
`alternateName`	Yes
`startingLevels`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds genuine context by enumerating the static template's sections and flagging 'Not legal advice', which shapes how an agent should present the output.

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?

One front-loaded sentence led by the verb and resource, with no filler. The parenthetical section enumeration is long but earns its place by helping the agent judge relevance; a shorter version would leave the agent guessing at contents.

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?

This is a simple, read-only, zero-required-parameter content fetch with a full output schema, and the description still specifies what the payload contains and includes the legal disclaimer. Nothing an agent needs in order to call it correctly is missing.

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?

The single optional 'lang' parameter has 100% schema description coverage, including the enum values and the 'omit to get both' behavior, so the description carries no additional parameter meaning. 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?

Names a specific verb and resource (returns the agreement sheet / afsprakenkaart) and enumerates its contents (sections 1-5, three starting levels, ten-question exit test, JSON Schema), so an agent knows exactly what document this yields and can distinguish it from get_approach or get_offers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers it should call this when it needs the written agreement template, but there is no explicit when-to-use framing, no mention of how it differs from the sibling content tools, and no exclusion such as 'not for the ownership check – use get_ownership_check'.

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

All OwnYourAgent Agentvoordeur tools Inspect

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

Need Help?