Skip to main content
Glama

Worklittle Jobs

Jobs · Create Sign In Link

create_sign_in_link

Jobs — Create a one-time link that opens worklittle.com signed in as the user (used by the app's buttons).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

'One-time' is a genuinely useful behavioral disclosure that reinforces the non-idempotent annotation and tells the agent the link cannot be reused. Beyond that, it omits key behavior: whether a session must already exist, whether the link expires, and that the returned link is a credential that grants account access. Annotations cover safety (non-destructive, closed-world) but not these operational traits.

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?

A single sentence with zero filler: the outcome and its consumer are front-loaded. The 'Jobs —' prefix is a consistent title convention rather than wasted words.

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 no parameters and an output schema present, the description needn't explain return values, so it is nearly complete. The remaining gap is the security context — that the generated link is a bearer credential granting signed-in access — which an agent should know before surfacing or storing 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?

The tool takes zero parameters, so the schema needs no elaboration and the description correctly adds none. Baseline 4 applies since there is nothing for the description to compensate for.

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?

Names a specific verb and resource ('Create a one-time link') and adds the concrete outcome: a link that opens worklittle.com signed in as the user. No sibling tool does anything similar, so explicit differentiation isn't needed, but it also doesn't say what it operates on (which user) or how the identity is determined.

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 'used by the app's buttons' hints at intended usage — an internal sign-in flow rather than a general-purpose tool — but there is no explicit when-to-use, when-not-to-use, or prerequisite (e.g., must already be authenticated, must not be shared). Usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources