Skip to main content
Glama

ci_create_binding

Authorize a CI workflow to deploy a project by submitting a signed delegation. Specify the GitHub subject, allowed events, and optional route scopes for deployment.

Instructions

Create a GitHub Actions CI/OIDC deploy binding by sending a locally signed delegation to the SDK. This MCP wrapper does not sign or broaden authority; the signed delegation defines the repository/branch or environment, allowed events/actions, and optional route_scopes. Without route_scopes, CI cannot deploy route declarations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID the CI binding may deploy to.
providerNoCI provider. V1 supports only github-actions; omitted defaults to github-actions.
subject_matchYesGitHub Actions OIDC subject match, e.g. repo:owner/repo:ref:refs/heads/main.
allowed_actionsYesAllowed CI actions. V1 supports only deploy.
allowed_eventsYesAllowed GitHub event names, typically push and workflow_dispatch.
route_scopesNoOptional route delegation scopes, normalized by the SDK. Use exact paths like /admin or final wildcard prefixes like /api/*. Omit or pass [] for no CI route authority.
github_repository_idNoNumeric GitHub repository id to pin the binding to, or null if absent.
expires_atNoOptional ISO timestamp when this binding expires.
nonceYesLowercase hex nonce included in the signed delegation.
signed_delegationYesBase64 SIGN-IN-WITH-X delegation signed locally by the allowance wallet. This MCP tool does not sign; it only sends the signed delegation to the SDK.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly states that the tool only sends a signed delegation and does not sign or broaden authority. It discloses the effect of omitting route_scopes. However, it could be improved by mentioning error conditions or return value.

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?

The description is two sentences, front-loaded with the purpose in the first sentence. Every word adds value, and there is no redundancy or unnecessary information.

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?

The description adequately explains the core function and the delegation mechanism. It covers key constraints (no signing, route_scopes requirement). However, it lacks information about the return value or state, which is not provided in an output schema, so some completeness is lost.

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?

Schema coverage is 100%, providing detailed parameter descriptions. The description adds value by explaining the overall flow and the role of signed_delegation. It also clarifies route_scopes semantics (exact paths or wildcard prefixes), going beyond schema details.

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 clearly states the verb 'Create' and the resource 'GitHub Actions CI/OIDC deploy binding', with the mechanism 'sending a locally signed delegation'. It distinguishes from sibling tools like ci_get_binding, ci_list_bindings, and ci_revoke_binding by specifying the creation action.

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?

The description explains that the tool does not sign or broaden authority, and it clarifies that without route_scopes the CI cannot deploy route declarations. It provides context for when to use the tool but does not explicitly mention when not to use it or name alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kychee-com/run402'

If you have feedback or need assistance with the MCP directory API, please join our Discord server