Conecto

Get a link to the team overview

hr_dashboard_link

Read-onlyIdempotent

A one-time link to HR at a glance: who works here, who is out today and in the next 14 days, leave waiting for a decision, open tasks, and who starts or leaves in the next 30 days. Only when the person you work for asks to see it themselves: answer who is out and decide leave with HR's own tools first, and offer a link when they would rather look, making it once they say yes. The page is made when it opens, from HR's own reads as this key, so it shows only what this key may see: the same page as account_dashboard_link with area hr. It opens once and keeps for an hour; an unopened link ends after 7 days. Free. Free.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing that the link is one-time, opens once, lasts for an hour, expires unopened after 7 days, is generated on open from HR's reads with scoped visibility, and costs nothing. This is exactly the operational context an agent needs before minting a link.

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?

The description is front-loaded and mostly earns its space, but it includes a duplicated 'Free. Free.' and has some run-on phrasing. This is a minor efficiency flaw rather than a structural problem.

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?

With zero parameters, rich annotations, and no output schema, the description covers purpose, usage rules, visibility scope, link lifetime, and generation behavior. Nothing essential is missing for an agent to decide whether and how to call it.

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?

There are no parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly does not invent any.

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?

States a specific verb/resource (one-time link) and describes exactly what page it points to: who works here, who is out, pending leave, tasks, and starts/leaves. It also distinguishes itself from account_dashboard_link by saying it is the same page with area hr.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule: only when the person you work for asks to see it themselves. It also names the preferred alternative path (use HR's own tools for who-is-out and leave decisions first) and says to offer the link only when they would rather look.

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

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