Skip to main content
Glama
Sign In
appforshare-mcp

appforshare-mcp

Official
by appforshare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Latest build

latest_build
Read-only

Fetch the current build matching app, platform, project, or channel filters and return its install link, release notes, and store readiness findings.

Instructions

The newest build matching the filters, with its install link, release notes and store readiness findings.

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

Input Schema

NameRequiredDescriptionDefault
appNoBundle id (iOS) or package name (Android)
channelNoChannel name such as beta or live: builds in that channel, newest put in first
projectNoProject id from list_projects
platformNoOnly iOS or only Android builds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the response payload (install link, release notes, store readiness findings), which matters because there is no output schema. It stops short of stating empty-result behavior or ordering guarantees.

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 front-loaded sentence with no filler: selection rule first, returned artifacts second. Every clause carries information an agent cannot get from the schema.

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 four-optional-parameter read tool with no output schema, the description covers what is returned and how selection works. Remaining gaps are minor: what happens with zero matches, and how filters combine when several are supplied.

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%, so each of the four optional parameters (app, channel, project, platform) is already documented in the schema, including the channel ordering note. The description's 'matching the filters' adds no syntax or semantics beyond that, so the baseline 3 applies.

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?

States a specific resource and selection rule: 'the newest build matching the filters,' and enumerates what comes back (install link, release notes, store readiness findings). That implicitly separates it from list_builds (many) and build_info (a specific build), though no sibling is named explicitly.

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?

Usage is only implied by the phrase 'newest build matching the filters' — an agent can infer this is the one-shot 'what's the latest?' query. There is no explicit when-to-use versus build_info or list_builds, and no statement about behavior when nothing matches the filters.

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