JooVoice

JooVoice profile

get_profile

Read-onlyIdempotent

The JooVoice account this connection is signed in to: a stable id, the name businesses hear, the sign-in email and a label to tell accounts apart. Read-only; takes no arguments.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`id`	Yes	Opaque, stable identifier for this JooVoice account and user.
`name`	No	The name businesses hear when JooVoice calls.
`email`	No	The account’s sign-in email, for display.
`nickname`	No	A label that tells this account apart from others.
`maintenance`	No	Present only during scheduled maintenance: calls may be paused until endsAt.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedOutput schema / properties / maintenance

Added value: +{
+  "description": "Present only during scheduled maintenance: calls may be paused until endsAt.",
+  "properties": {
+    "active": {
+      "type": "boolean"
+    },
+    "endsAt": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful scope context ('this connection is signed in to') and repeats that it is read-only and takes no arguments, but it does not add deeper behavioral detail such as auth requirements or rate limits.

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?

The description is a single, front-loaded sentence that identifies the account context, enumerates the returned fields, and notes it is read-only and argument-free. There is no filler or redundancy.

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?

Given the rich annotations, output schema, and zero parameters, the description is largely complete for invoking the tool. Its only notable gap is not clarifying its relationship to potentially overlapping account-checking siblings, which slightly limits routing completeness.

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?

The tool has zero parameters, so the baseline is 4. The description explicitly states 'takes no arguments,' which matches the empty schema and reinforces that no input is needed.

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 clearly identifies the resource as the JooVoice account tied to the current connection and lists the fields returned (stable id, business-facing name, sign-in email, label). It is specific enough to distinguish from most sibling tools, though it does not explicitly contrast with check_account.

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?

The description gives no explicit guidance on when to use get_profile versus alternatives such as check_account or read_settings. The intended use is implied by the name and account-focused wording, but there are no when/when-not conditions or named alternatives.

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

All JooVoice 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?