Veqen: AI cost monitoring and protection

Single sign-on

single_sign_on

action get, link (domains: your company's email domains), portal (intent sso, domain_verification or dsync: a WorkOS link for whoever administers the identity provider), refresh (read domain verification) or save (enforced, default_role, groups: directory group to role). Changes are for owners. Confirm before requiring SSO.

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

Input Schema

Name	Required	Default
`action`	No	get
`groups`	No
`intent`	No	sso
`domains`	No
`enforced`	No
`default_role`	No	member

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

B3/5.0

Behavior4/5

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

Annotations already mark the tool as not read-only, not destructive, and non-idempotent. The description adds useful behavioral context beyond annotations: 'Changes are for owners' discloses an authorization requirement, and 'Confirm before requiring SSO' warns about a consequential action. It still does not explain per-action side effects or reversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense run-on sentence with nested parentheticals, making it hard to parse. It is short, but the structure is poor and the action semantics are not front-loaded or easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-action tool with six parameters and no schema descriptions, the description provides only partial context. It does not explain which parameters are required for which action, what each action returns or changes, or the default behavior of get. An output schema exists, so return-format explanation is not required, but action-level completeness is still 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?

Schema description coverage is 0%, so the description must carry parameter meaning. It partially does: domains are tied to company email domains, groups are tied to directory group-to-role mapping, and intent is tied to portal modes. But enforced and default_role remain unexplained, and the action-to-parameter relationships are only implied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists the five action values (get, link, portal, refresh, save) and parenthetically hints at what each does, but never states a clean top-level purpose like 'manage SSO configuration.' An agent can infer this is an SSO management tool, but the action prose is fragmented and does not clearly distinguish it from siblings such as access or organization.

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?

The parenthetical action hints imply when each action applies, and 'Changes are for owners. Confirm before requiring SSO' gives a permission and caution note for save. However, there is no explicit when-to-use versus alternatives guidance, and the action routing is left implicit.

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

All Veqen: AI cost monitoring and protection tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?