tslink

by anydoor7

Overview Schema Source Related Servers Discussions Admin

Hybrid

Deny an access request

requests_deny

DestructiveIdempotent

Deny an in-scope access request as portal owner or people manager, optionally with a reason shown to the visitor.

Instructions

Current portal owner (owner or people-manager role): deny an in-scope request, optionally with a short reason shown to the visitor. Exact retries replay; different or stale decisions conflict.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "requests_deny"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`reason`	No

Output Schema

Name	Required	Description	Default
`changed`	Yes
`request`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses retry semantics ('exact retries replay'), conflict behavior on divergent or stale decisions, the authorization role required, and that the reason is surfaced to the visitor. The annotations only assert idempotent/destructive hints; the description explains what those mean operationally and adds the visitor-visibility consequence.

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?

One dense sentence with the actor and action front-loaded, followed by retry/conflict semantics. Every clause adds distinct information; nothing is padding.

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 an output schema present, return values need no explanation, and the description covers authorization, idempotency, conflict, and reason visibility. The main omission is any hint of what 'in-scope' means or what a conflict response requires the agent to do next, which leaves a small operational 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 0%, so the description carries the burden; it does clarify that 'reason' is optional, capped in spirit by 'short', and visible to the visitor, which is meaningful beyond the bare string/maxLength schema. However, 'id' is left entirely unexplained, so the description only partially compensates for the coverage gap.

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 and resource ('deny an in-scope request') plus the acting role, which cleanly separates it from the sibling requests_approve and requests_list. An agent can pick this tool without opening any schema.

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?

Gives a concrete precondition ('current portal owner, owner or people-manager role') and scope ('in-scope request'), which is real when-to-use guidance. It stops short of explicitly contrasting with requests_approve or stating when denial is inappropriate, so it is clear context rather than full routing.

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