VeriTeknik

List contracts

list_my_contracts

Read-onlyIdempotent

Lists the company's service contracts with period, renewal date, live net values per currency and status. Amounts require billing visibility; single-value fields are null for multiple currencies. Optional status filter: active, expired, terminated, draft, pending_signature, customer_signed, fully_signed, cancelled. Optional limit for paging (default 20). Call it when the user asks which services are under contract or when one renews.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Number of contracts to return (default 20).
`status`	No	Filter by contract status: active, expired, terminated, draft, pending_signature, customer_signed, fully_signed or cancelled.

Output Schema

Name	Required	Description	Default
`data`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 25, 2026
- removedOutput schema / properties / data / properties / items / items / properties / autoRenew / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / items / items / properties / autoRenew / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / items / items / properties / currency / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / items / items / properties / currency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / items / items / properties / status / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / items / items / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / items / items / properties / valuesCurrency / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / items / items / properties / valuesCurrency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / items / items / properties / valuesIncomplete / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / items / items / properties / valuesIncomplete / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

Changed2 schema fields changedOct 17, 2026

removedOutput schema / properties / data / properties / items / items / properties / createdAt

Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

changedOutput schema / properties / data / properties / items / items / required

Previous value: -[
-  "id",
-  "contractNumber",
-  "title",
-  "status",
-  "startDate",
-  "endDate",
-  "monthlyValue",
-  "yearlyValue",
-  "totalValue",
-  "valuesIncomplete",
-  "valuesByCurrency",
-  "valuesCurrency",
-  "currency",
-  "autoRenew",
-  "createdAt",
-  "isExpired"
-]New value: +[
+  "id",
+  "contractNumber",
+  "title",
+  "status",
+  "startDate",
+  "endDate",
+  "monthlyValue",
+  "yearlyValue",
+  "totalValue",
+  "valuesIncomplete",
+  "valuesByCurrency",
+  "valuesCurrency",
+  "currency",
+  "autoRenew",
+  "isExpired"
+]

First observedOct 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds context annotations can't express: amounts require billing visibility, and single-value fields are null when multiple currencies exist, plus a default page size of 20. Return shape is covered by the output schema, so no penalty there.

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?

Purpose and the returned field set are front-loaded, followed by the permission caveat, the filter, and the trigger. It is dense and mostly earns its words, but re-listing all eight status values duplicates the schema and adds length without new 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 two-parameter read-only list tool with an output schema and full annotation coverage, the description is nearly sufficient: it covers permission requirements, null semantics for multi-currency, paging default, and invocation triggers. Only ordering/sort behavior is left unstated, a minor gap.

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 coverage is 100% and both parameters are fully documented in the schema, including the status enum values and the default limit of 20. The description restates the same status list and default limit rather than adding new meaning, so baseline 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 gives a specific verb+resource ('Lists the company's service contracts') and enumerates the fields returned (period, renewal date, live net values per currency, status), so the agent knows exactly what this tool yields. It doesn't name the sibling it complements (get_contract_details) or explicitly distinguish list-vs-detail, so it stops short of a 5.

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 closing sentence gives concrete invocation triggers: 'when the user asks which services are under contract or when one renews.' That is clear usage context. It doesn't state when not to use it (e.g., for a single contract, use get_contract_details), which is the only missing piece.

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

All VeriTeknik 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.