Examova — Exam Prep

Get Signup Links

get_signup_link

Read-onlyIdempotent

Links to start using Examova: free demo exam, free account (5 questions/day) and Pro pricing; optionally deep-linked to a certification.

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_signup_link"
  }
}

Input Schema

Name	Required	Description	Default
`certification`	No	Certification slug, code or name, e.g. "pmp", "cips-l4", "prince2-foundation". Call list_certifications for the live list.

Output Schema

Name	Required	Description	Default
`demoUrl`	Yes
`pricingUrl`	Yes
`registerUrl`	Yes
`certificationUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / certification / description

Previous value: -"Certification slug, code or name, e.g. \"pmp\", \"cips-l4\", \"prince2-foundation\", \"business-english\". Call list_certifications for the live list."New value: +"Certification slug, code or name, e.g. \"pmp\", \"cips-l4\", \"prince2-foundation\". Call list_certifications for the live list."

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / certification / description

Previous value: -"Optional certification slug to deep-link"New value: +"Certification slug, code or name, e.g. \"pmp\", \"cips-l4\", \"prince2-foundation\", \"business-english\". Call list_certifications for the live list."

addedInput schema / properties / certification / maxLength
```
Added value: +80
```

Changed1 schema field changedJul 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "certificationUrl": {
+      "type": "string"
+    },
+    "demoUrl": {
+      "type": "string"
+    },
+    "pricingUrl": {
+      "type": "string"
+    },
+    "registerUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "demoUrl",
+    "registerUrl",
+    "pricingUrl"
+  ],
+  "type": "object"
+}

First observedJul 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds useful scope context (which three link targets exist, and that the certification deep-link is optional). It doesn't mention link format, base domain or fallback behavior for an unrecognized certification, which would have raised the score.

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?

A single dense sentence with no filler; the three link targets are front-loaded ahead of the optional certification modifier. Slightly compressed by the parenthetical, but nothing is wasted.

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?

With one optional, fully documented parameter and an output schema, the description covers everything needed to invoke it correctly. Only minor gaps remain, such as behavior when the certification identifier does not resolve.

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%, and the parameter already explains accepted forms (slug, code or name) plus the list_certifications pointer. The description only adds that the deep-link is optional, which is marginal but consistent value over the schema. 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 names the resource concretely: links for a free demo exam, a free account (with the 5 questions/day limit) and Pro pricing, plus an optional certification deep-link. That is specific enough to separate it from get_pricing (price details) and list_certifications. It is a noun phrase rather than an explicit verb, but the deliverable is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to call it versus siblings such as get_pricing or list_certifications. The agent can infer intent (user wants to sign up or be pointed to a signup/pricing page), but nothing is said about preconditions or exclusions.

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

All Examova — Exam Prep 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?