Skip to main content
Glama
Sign In
PyPen MCP

PyPen MCP

by eyenoticeall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

session_make_request

Execute HTTP requests using the browser's current session to access authenticated endpoints without manual credential handling.

Instructions

Make an HTTP request using the browser's session (inherits cookies/auth)

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": {
      "url": "<url>"
    },
    "name": "session_make_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequest URL
methodNoHTTP methodGET
headersNoRequest headers
bodyNoRequest body
paramsNoQuery parameters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. The description only mentions inheriting cookies/auth but omits critical behaviors like redirect handling, response format, error handling, rate limits, or method support. For an HTTP request tool, this is insufficient.

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?

Single sentence, front-loaded key information (purpose and context), no wasted words. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description lacks details on return values, error handling, or examples. For a tool with 5 parameters and nested objects, the description is too sparse to be considered complete.

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 100%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions aside from the session context. No improvement over schema.

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?

The description clearly states the tool makes an HTTP request using the browser's session, inheriting cookies/auth. It distinguishes from sibling session and network tools by specifying the request-making action with session context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like network_enable_interception or browser_navigate. No prerequisites or when-not-to-use are mentioned.

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