Skip to main content
Glama

Finish Crunch login

crunch_auth_complete

Completes a Crunch login by exchanging the authorization code or redirected URL for tokens and saving them to the token file.

Instructions

Finish a login started with crunch_auth_start by exchanging the authorisation code for tokens, which are saved to the token file. Pass the full URL the browser was redirected to, or just the code together with the state crunch_auth_start returned.

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": {
      "redirected_url": "<redirected_url>"
    },
    "name": "crunch_auth_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoThe state crunch_auth_start returned; only needed when redirected_url is just the code
redirected_urlYesThe full URL from the browser's address bar after clicking Allow (it contains code= and state=), or just the code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent operation; the description adds the concrete side effect of writing tokens to the token file, which is genuinely useful. It does not warn that an authorisation code is typically single-use, so retry/re-run behavior stays opaque for a non-idempotent tool.

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?

Two tight sentences with the prerequisite first and the parameter options second; 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?

For a two-parameter auth-completion tool with no output schema, the description covers the prerequisite, the side effect, and both input forms. Only the notion of what happens on an expired or already-used code is left unstated.

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 100%, including the 'state only needed when redirected_url is just the code' rule, so the description largely restates what the schema already documents. The framing of the two input modes is a mild convenience but adds no new semantics.

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?

The description pairs a specific verb ('Finish a login') with the exact resource and mechanism: exchanging the authorisation code for tokens saved to the token file. It names crunch_auth_start as the prerequisite, so an agent can distinguish it from the other auth siblings without opening a 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?

It clearly states the context of use: only after a login started with crunch_auth_start, and gives the two acceptable input shapes (full redirect URL vs. code plus state). It does not address crunch_auth_status or what to do if the exchange fails, so a small gap remains.

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

Deploy Server

Other Tools